SCHED-737: Include PR number in merge-back branch name to avoid collisions #2021
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
…sions When multiple PRs are created from the same feature branch, the merge-back workflow would fail because it tried to create a branch with the same name. Adding the PR number ensures uniqueness.
theyoprst
force-pushed
the
yoprst/SCHED-737/fix-merge-back-unique-branch
branch
from
b11087b to
086425a
Compare
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.
Problem
When multiple PRs are created from the same feature branch, the merge-back workflow would fail because it tried to create a branch with the same name. Adding the PR number ensures uniqueness.
Solution
Add a PR_NUMBER to the branch name.
Testing
None
Release Notes
None