feat: filter unused blobs when cloning repo - #217
Merged
Conversation
Contributor
Coverage report
Test suite run success218 tests passing in 18 suites. Report generated by 🧪jest coverage report action from 0e3aa86 |
lampajr
approved these changes
Jul 21, 2026
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
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.
Description
Instructs git to do a blob-filtered clone.
This can potentially save a lot of time, traffic and space, depending on the repo in question, and it does no harm if not.
How Has This Been Tested?
Deployed on our Forgejo instance and works fine.
Git gracefully falls back to a full clone if the remote does not support filters, so this is pretty risk free.
Checklist
Merge criteria: