-
Notifications
You must be signed in to change notification settings - Fork 2.7k
feat(git): support shallow fetch for Git CLI backend #16156
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
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
This is a preparation for git backend interop tests
Not a shallow clone test and we've covered it in normal git tests.
Make sure each backend is actually used
The newly added tests also ensure the interop between each backend
|
Unsure if anything in this commit would be relevant: epage@9af85fd |
epage
approved these changes
Oct 27, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to merge if you don't see anything relevant in the commit I shared
|
Thanks for sharing! I am a bit lazy to rewrite Git history now. Will do a post-cleanup and cherry pick your changes then :) |
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 28, 2025
### What does this PR try to resolve? Cherry-pick some test generalization from <epage@9af85fd> See <#16156 (comment)> `fetch_dep_then_fetch` is a bit tricky to generalize, so leave it there. ### How to test and review this PR?
bors
added a commit
to rust-lang/rust
that referenced
this pull request
Oct 29, 2025
Update cargo submodule 11 commits in 344c4567c634a25837e3c3476aac08af84cf9203..6c1b6100343691341b9e76c5acc594e78220f963 2025-10-15 15:01:32 +0000 to 2025-10-28 16:27:52 +0000 - feat(build-analysis): JSONL-based logging infra (rust-lang/cargo#16150) - feat: support array of any types in Cargo config (rust-lang/cargo#16103) - test(git): add more fetch-index backend interop (rust-lang/cargo#16162) - feat(git): support shallow fetch for Git CLI backend (rust-lang/cargo#16156) - Fix mdman to not incorrectly strip `<p>` tags (rust-lang/cargo#16158) - chore(triagebot): enable range-diff and review-changes-since (rust-lang/cargo#16152) - Avoid specifying which version will change behavior (rust-lang/cargo#16153) - Make shell completion variables private. (rust-lang/cargo#16144) - More warning conversions (rust-lang/cargo#16143) - Bump openssl-src to 300.3.5.4+3.5.4 (rust-lang/cargo#16140) - build: remove duplicate dependency, consolidate over unicode-ident (rust-lang/cargo#16137)
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.
What does this PR try to resolve?
Fixes #14956
How to test and review this PR?
This is done with some test generalization, so that we can test more backend interop in the future when libgit2 support
file://protocol shallow clones.In the future we should add container tests for at least gitoxide and libgit2 backend to ensure they really work with https protocol