Add --tag-pattern option to the release command
#79
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
Json output
Author
|
I created this PR in the wrong repo - I meant to create it in my fork: cucumber#2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Some projects use a
vprefix in front of tags, as illustrated by the older tags in this changelog.The KAC spec does not mandate a particular format for git tags, but the example in the spec uses a
vprefix. It seems we should allow some flexibility around this, to cater for different practices.This PR adds a new
--tag-formatoption where the user can specify a printf format (for examplev%s).This should allow us to create correct links in the bottom of the changelog.