Fix get default branch failed when Git has not set trace branch #60
Conversation
This file contains 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
kayw-geek
force-pushed
the
bugfix/fix-no-trace-branch
branch
from
6086a21 to
d748fc9
Compare
kayw-geek
added a commit
to kayw-geek/monorepo-builder
that referenced
this pull request
Oct 19, 2023
…ch (symplify#60)" (symplify#61) This reverts commit 30e6afb.
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.
This pull request solved get the default branch failed when Git's tracking branch has not been explicitly set.
Prior to this fix, the method
getDefaultBranch()would fail in instances where a tracking branch was not properly setup in Git, and as a result, retrieving the default branch would not be possible.Now, I will execute the command that
git remote set-head origin -ato set the tracking branch to avoid the error reproduced