Prevent git clone from fetching blobs #12
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
|
I'm not well versed in these intricacies about Git. I think I need to add some CI tests to make sure such changes don't change the output of the command (e.g. the data file is still the same). |
Sync with upstream
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.
git clone does a
fetchafter a successful clone, which defeats the purpose of doing--filter=tree:0as it seems like git will still fetch the file contents from the remoteAdding
--no-checkoutshould effectively prevent thisfetchand leave the clone without any blobs, just having the.gitdirectoryI am not 100% sure this is necessary but from testing on my own fork, this seems to do the trick (my fork has other changes to the git clone command to work with our branching structure).