docs: Suggest a blobless clone instead of a shallow clone #64693
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
GitHub recommends blobless clones over shallow clones: https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/ > For these reasons we do not recommend shallow clones except for builds that delete the repository immediately afterwards. Fetching from shallow clones can cause more harm than good! I've been using blobless clones for development for the last couple weeks. The blobless clone has the benefit of including the full repository history (for the cloned branch). Tools like `git blame` will be slower as git fetches the related blobs on-demand. Benchmarks (using all the flags in the docs): - The blobless clone is faster on my machine, taking 11.1 seconds versus 13.1 seconds for the shallow clone. - The blobless clone takes up 256M on disk, versus 244M for the shallow clone. It's worse, but not by much.
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
bgw
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
feedthejim,
ztanner and
wyattjoh
as code owners
timneutkens
approved these changes
Apr 18, 2024
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
GitHub recommends blobless clones over shallow clones: https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/
I've been using blobless clones for development for the last couple weeks. The blobless clone has the benefit of including the full repository history (for the cloned branch). Tools like
git blamewill be slower as git fetches the related blobs on-demand.Benchmarks (using all the flags in the docs):