-
Notifications
You must be signed in to change notification settings - Fork 698
cli: git fetch: fall back to remote fetch refspecs when -b not specified #7275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
a14cdc1
to
7ee1af2
Compare
I was able to figure it out, git insists on Unix style separators even on windows and I found a |
7ee1af2
to
440eede
Compare
yuja
reviewed
Aug 19, 2025
440eede
to
3a044ec
Compare
3a044ec
to
902ccad
Compare
yuja
reviewed
Aug 21, 2025
902ccad
to
e133af8
Compare
yuja
reviewed
Aug 23, 2025
e133af8
to
28ed0a7
Compare
yuja
approved these changes
Aug 24, 2025
This changes the behavior of git fetch to respect the fetch refspecs configured on the remote. This is handy for projects which use customized fetch refspecs (e.g. only fetch certain patterns, but not all branches) but without having to remember and repeat all the patterns by hand on the CLI Fixes #5323
28ed0a7
to
38b2ef7
Compare
2 tasks
ipetkov
added a commit
that referenced
this pull request
Sep 1, 2025
Now that #7275 it's worth mentioning that simple fetch refspecs will (now) be respected when other branches are otherwise not specified on the CLI
ipetkov
added a commit
that referenced
this pull request
Sep 1, 2025
Now that #7275 has merged it's worth mentioning that simple fetch refspecs will (now) be respected when other branches are otherwise not specified on the CLI
github-merge-queue bot
pushed a commit
that referenced
this pull request
Sep 1, 2025
Now that #7275 has merged it's worth mentioning that simple fetch refspecs will (now) be respected when other branches are otherwise not specified on the CLI
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.
Checklist
Fixes #5323
Only fetch refspecs matching a very conservative set of patterns (i.e. no branch or remote renames, must be a forced refspec for
refs/heads/
, etc) is supported and everything outside of that will be (warned about) and ignored. We can always expand these in the future but for now it would be good to avoid ambiguities about how branch renaming ought to be handled.If applicable:
CHANGELOG.md
README.md
,docs/
,demos/
)cli/src/config-schema.json
)