Automate to prepare release note with next version #1061
Merged
Conversation
This file contains hidden or 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
mokuzon
approved these changes
Nov 25, 2024
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.
To create release notes, the following steps are necessary, but currently, they cannot be enforced:
This change automates the creation of a draft release, forcing the release creator to complete steps 1 and 2. The version is automatically determined with a
vprefix by simply choosing from major/minor/patch. The title will be a combination of steps 1 and 2.About 3, drafted note shows actor name, so I believe almost all of us can realize we need to revise note.(but I know it's not perfect)
When we run the workflow
When the workflow is executed, a draft like the following will be created.
By revising this and making a release, it will result in the same as usual.
