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.
#821
⚡ Summary
Git LFS is an opt-in feature that lets people store large files outside a git repository, saving only pointers to them in the git repository itself.
Git does not use LFS by default. One must manually specify files and file patterns using the
.gitattributes
file.I've found that LFS adds about 2.2 seconds when running lefthook in my employer's large git repo.
My small benchmark
Considering the ~500 engineers in my company, and assuming an average of 1
git checkout
per day (I assume this is a low estimate, but I don't have metrics on this), we'd save 6.1 hours of engineering time every month.NOTE
I'd personally recommend that we rework this feature—that we change the flag to
enable_lfs
and disable LFS hooks by default. I'm more than happy to do so.Because LFS is fully opt-in, and because of its poor performance in large repositories, I don't believe it makes sense to enable this feature by default.
ALSO NOTE
I disabled LFS for this project as well since it's not needed here (see "chore" commit). I assume you will want me to revert that change! I'm more than happy to 😅.
☑️ Checklist