ci: add backmerge #1457
Merged
ci: add backmerge #1457
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
Thanks for opening this pull request!
|
|
🎉 This change has been released in version 3.4.2-alpha.1 |
|
🎉 This change has been released in version 3.4.2 |
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.
New Pull Request Checklist
Issue Description
The release automation framework "semantic-release" relies on previous tags on the branch from which a release is triggered to determine the next version to be released. It does not recognize tags on other branches, hence after merging a (prerelease) branch into another branch the branch that was merged into the other branch also needs to be rebased onto the branch it was merged into afterwards.
For example: after merging branch
alphaintobetato trigger a beta prerelease, the branchalphaneeds to be rebased on branchbeta. Due to this behavior, auto-release processes of a repo cannot run in parallel, even if they concern different branches.Related issue: #n/a
Approach
Automatically rebase branch after release.
TODOs before merging
n/a