Git fetcher: Don't create refs when fetching by revision #12386
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.
Motivation
This fixes a couple of issues with the Git fetcher:
When fetching by revision, don't create a ref named
refs/head/<revision>
. (This was caused by doinggit fetch <revision>:<revision>
.) This is unnecessary and triggers the next bug.When parsing the output of
git ls-remote --symref
, make sure that the first line referencesHEAD
, otherwise a line likewill cause
5c44...
(created by the previous bug) to be interpreted as a ref, leading to errors likefile://
URLs. Git interprets them as part of the file name, so passing parameters likerev
breaks. Only relevant for testing (when_NIX_FORCE_HTTP
is set) and local bare repos.Context
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.