feat: handle release branching strategy #1359
Closed
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.
Hi! First of all, thank you for building this GH action. I've been using it for a while, and it works great!
I need to set it up in a project that uses the "Release Branching Strategy" (see http://releaseflow.org/).
In this flow, we have a unique branch name for every release, like so:
release-1.0.0
--> tag1.0.0
release-1.1.0
--> tag1.1.0
To find the latest release that is not a hotfix (i.e. filter out releases created from
hotfix-**
branches), we would like to filter releases by testing their targets against a regex.I've allowed myself to make this simple change that renders
release-drafter
compatible with this use case.Let me know what you think. Thanks!