-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implemented automation workflows for change notes and release building #78
Open
DC23
wants to merge
17
commits into
orffen:main
Choose a base branch
from
DC23:#76-Release-Automation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
orffen#76 release automation
I don't think draft releases are what we want
Removing default artifacts and fixing zip path in manifest
fixed bug in release build workflow - the zip file download url was incorrect
renaming zip to basicfantasyrpg.zip
DC23
changed the title
#76 release automation
Implemented automation workflows for change notes and release building
Nov 28, 2024
I updated the PR title. It's an example of the type of title that works really well with the release drafter workflow. The title is a single active sentence that describes to a reader the key change that the PR implemented. It will automatically show up in the release notes, categorised by whatever label you add to the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've implemented two release automation workflows.
.github/release-drafter.yml
. In the categories section you will see the mapping between labels and categories. I've used the categories I use on my other project. You can change these to suit. You don't have all the labels yet. Add what you need, adjust categories and it will all work. Note that a PR should only have a single label, or it gets added to the release notes twice.If you change the PR label or title later, the workflow can be run manually and it will update the notes while they are still in draft.
For both, I have the workflows running with the minimum permissions possible, so you can reduce the default Actions workflow permissions from the default "read and write" to "read".
These two PRs should have no overlapping files, but you probably still want to merge this one first.