Repository navigation
release-drafter - #33
Merged
Merged
Conversation
Signed-off-by: Artem Bortnikov <[email protected]>
George Gaál (gecube)
approved these changes
Mar 18, 2024
Collaborator
|
Artem Bortnikov (@aobort) fix pre-commit errors, please |
Signed-off-by: Artem Bortnikov <[email protected]>
Kirill Ilin (sircthulhu)
approved these changes
Mar 18, 2024
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
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.
The auxiliary GH action to setup release drafts and update change log accordingly. Configured with autolabeler, so the PRs will be labeled according to the PR branch name and/or files changed:
dependencieschoredocumentationenhancementfeaturebugfixbugfixapi-changecontrollersBased on labels release draft will be updated with 'Features', 'Bug Fixes' and 'Maintenance' categories which will include corresponding PR's title.
It's also possible to manage release draft's version by applying
major,minorandpatchlabels on PR. By default the version will be the next patch version after the last release, v0.0.1 if none.