Add shallow clone support (--depth) #7
Draft
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.
Problem
When cloning repositories with many refs (250K+ tags/branches), JGit sends "have" lines for all local objects during fetch negotiation. This creates massive request payloads that cause RSocket fragmentation issues.
Solution
Add shallow clone support (
--depth 1) which:API
Changes
Transport.javadepth,deepenSince,deepenNotsfields with accessorsCloneCommand.javasetDepth(),setShallowSince(),addShallowExclude()FetchCommand.javasetDepth(),setShallowSince(),addShallowExclude()BasePackFetchConnection.javashallow-inforesponse, write.git/shallowFetchProcess.javaGitProtocolConstants.javaSECTION_SHALLOW_INFOconstantTesting
Tested manually against GitHub:
Notes
This is a simplified implementation compared to official JGit 6.x:
--unshallowor deepening existing shallow clones.git/shallowfile (vs ObjectDatabase API)