Repository navigation
Make clones faster when we know ahead of time we need the full history - #180
Merged
Merged
Conversation
This addresses the poor performance of iterative shallow deepening in the case we add new rules and need to reprocess the full history.
This helps make iterative shallow deepening more performant. The previous commit helped make shallow deepening less necessary. A shallow deepen is now only necessary when more than DEFAULT_SHALLOW_DEPTH commits are merged since the last run. For the size of repositories I'm aiming to support, 200 seems like an okay heuristic.
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
1 participant
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.
Closes #176