Add support for reference repository parameter #1400
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
Spiritaine
approved these changes
Jul 9, 2023
|
does this work for git lfs? |
tbranch227
approved these changes
Aug 25, 2025
I believe it does. We use --reference with our own processes (not this action) and it's a big performance improvement and offloads work from the server and WAN links. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Git clone command added support for a local reference repository in order to minimize the network traffic and load on the git servers for big repositories. Adding support to specify such reference git repository in the checkout action.
The is very useful in big repositories hosted in GitHub Enterprise deployments that runs massive scales of CI jobs across distributed geographies.
Tested manually in my private GitHub Enterprise instances, but I lack the knowledge to create a unit test for this. Sharing to upstream so it can be taken from here, or pulled by other people needing it (see #22 and #687)