This repository has been archived by the owner on Oct 2, 2024. It is now read-only.
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 LFS is useful when we're putting big files that changes frequently and/or doesn't compress well, by replacing those blobs with pointers to each version, so cloning will only download a small data for each revision, which is the pointer differences.
This also means that it gives us few to no benefits in using LFS in our scenario where we never really modify our big files once we've committed them, and the bandwidth limitation on GitHub LFS service + Vercel auto-deployments for each commit makes this annoying to work with without getting an email reminder for our quota usage after only a couple of commits.