ci(workflow): Hasten checkout with blobless clones #354
Conversation
This file contains 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
In v4.1.0, actions/checkout recently introduced support for Git's partial clones. Partial clones are smaller than full clones (`fetch-depth: 0`), because they don't clone historical blobs and/or trees. In partial clones, Git operations will typically fetch data that isn't available locally as needed. Hence, prefer blobless clones, the partial clones that give the best performance overall, to full clones.
Kurt-von-Laven
force-pushed
the
workflow
branch
from
d001de5 to
4d1e37f
Compare
Kurt-von-Laven
changed the title
|
I experimented with both treeless and blobless clones, and they increased the runtime of the entire workflow by about 75% and 50%, respectively, so I am closing this pull request. |
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.
In v4.1.0, actions/checkout recently introduced support for Git's partial clones. Partial clones are smaller than full clones (
fetch-depth: 0), because they don't clone historical blobs and/or trees. In partial clones, Git operations will typically fetch data that isn't available locally as needed. Hence, prefer blobless clones, the partial clones that give the best performance overall, to full clones.