Offer to fetch more history when merge base fails in shallow clones#136
Merged
Offer to fetch more history when merge base fails in shallow clones#136
Conversation
When getMergeBase fails and the repository is a shallow clone, prompt the user to progressively deepen the clone until the merge base is found. Uses the VS Code Git API for fetching (proper auth support). Falls back to unshallowing as last resort. Also: - Limit diff entries to 10,000 to avoid performance issues - Add timing to git command log output
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.
When getMergeBase fails and the repository is a shallow clone, prompt the user to progressively deepen the clone until the merge base is found. Uses the VS Code Git API for fetching (proper auth support). Falls back to optional unshallowing as last resort.
Also: