feat: Release branch naming convention#19
Merged
Conversation
rimi-itk
reviewed
Jul 7, 2026
rimi-itk
left a comment
rimi-itk
left a comment
Collaborator
There was a problem hiding this comment.
This is great! I've been renaming hotfix brances manually a couple of times lately.
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
2 participants
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.
Using
gh itkdev changelog --release x.x.x to create a new patch release, the release branch is named hotfix/x.x.x
Due to the default woodpecker staging release setup, this will not trigger a release to staging.
Therefore, i propose that we only use the release/x.x.x naming convention, even if the original solution is more correct.
Updating the changelog manually is i pain, i love this tool 🫶