Add tag-prefix config option #997
Closed
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
mxj4
force-pushed
the
feat_tag_prefix
branch
from
b622ac1
to
38a1641
Compare
|
|
Sorry I moved to something else since release drafter do not work with our release workflow (need to release from any commit in repo, not just master HEAD). I see you already started with another similar PR, if you still need this I can turn it into a published PR. |
|
Looks like this has been implemented in #1092 |
|
fixed in #1092 |
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.
This config option makes it possible to filter previous releases by git tag name prefix, thus makes it possible to identify tags for a single component in a monorepo.