fix: add --limit=1 when determining branch copy source #1571
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
JohnstonCode
pushed a commit
that referenced
this pull request
Apr 19, 2022
JohnstonCode
added a commit
that referenced
this pull request
Apr 19, 2022
## [2.15.4](v2.15.3...v2.15.4) (2022-04-19) ### Bug Fixes * Add --limit=1 when determining branch copy source ([#1571](#1571)) ([593dfe5](593dfe5))
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.
When determining if a branch is a copy, the entire log is fetched, but only the first commit is checked. This is problematic if the branch is not a copy, and the commit log is massive. A large enough log will currently crash VS Code.
This fix limits pulling only the first log. Fixes #1539