Open
Conversation
…it to the integration branch.
…tory branch after merging it to the integration branch.
…l branch, it will be used as the integration branch (if no integration branch is in your config)
…into branch with the same name as the branch suffix if it exists.
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
1 participant
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.
Updated to use the current branch suffix as the preferred integration branch if such a branch exists.
For example, if your branch is:
feature-19711234-customer-sign-upthen when yougit-finish, it will try to merge intocustomer-sign-upif there is a local branch with that name. Otherwise it does business as usual (first checks git config, else defaults to master)