Improve Git performance when using SHA revisions #380
Merged
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
This change separates testing of sha and refs in the revisions and only uses the values "*sha" when a sha is intented.
If you're using a sha as your revision parameter and the current HEAD is already pointing at that sha, there's no need to do a git fetch. Making this change should significantly reduce the number of calls made to the remote Git server; since the catalog hasn't changed, you'll be up-to-date and not do the fetch call.
|
Passed on adhoc |
david22swan
approved these changes
Jun 19, 2018
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 using a SHA revision, a
git fetchdoes not need to be done if the current HEAD is already pointing to the requested SHA.