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
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.
This PR adds an option
-j/--jumbothat tells Git to create a shallow clone. The shallow date is the date of the latest commit on the repo's main branch minus three weeks.For now, the three week offset is not configurable. There needs to be some offset, to help make sure that Git fetches enough history for merges, but not so much that Git spends a long time downloading history. I'll see how three weeks works in practice.
In addition to the convenience of automatically setting a
--shallow-sincedate, gimmegit is able to tell Git to apply the same date when fetching feature/base branches. If--shallow-sinceis only applied to thegit clone, fetching additional branches can still bring in too much history. This means that-jis not equivalent to providing-- --shallow-since <date>.I suppose it would be possible to inspect any extra options, extract
--shallow-since, then include the same--shallow-sinceoption when fetching branches. I'm open to implementing that at some point if it would be valuable.This PR also includes a few small fixes and improvements to the code and docs.