Repository navigation
after merge, switch to base branch if available - #5251
Merged
Merged
Conversation
cliAutomation
added
the
external
samcoe
approved these changes
Mar 4, 2022
samcoe
left a comment
samcoe
left a comment
Contributor
There was a problem hiding this comment.
@bstncartwright This looks good to me. Thanks for adding a test!
samcoe
reviewed
Mar 4, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fixes #1096
After merging, previously we would switch to the default branch in the repo. With this change, after merging we switch our branch to the base branch of the pull request. If that is not available, then we fall back to the same behavior as before.