Use remote HEAD branches as default base branches#127
Merged
foriequal0 merged 3 commits intomasterfrom Aug 1, 2020
Merged
Conversation
4566848 to
450a39b
Compare
HEAD branches as default base branches
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.
resolves: #97
With this PR,
git-trimwill not use hard-coded default base branches anymore. It'll deduce a default base branch fromrefs/remotes/*/HEAD. Since git 2.28 has introducedinit.defaultBranchoption which can change the default branch name, it is required to makegit-trimmore resilient to different default branch names.Previous default base branches
develop,masterwere hardcoded while keeping git-flow in mind. Users of multi-base branching scheme, such as git-flow, should setgit config trim.bases develop,masterin order to use as it was.