Skip to content
This repository has been archived by the owner on Oct 2, 2024. It is now read-only.

chore: remove lfs dependency #50

Merged
merged 3 commits into from
Nov 29, 2023
Merged

chore: remove lfs dependency #50

merged 3 commits into from
Nov 29, 2023

Conversation

ignatiusmb
Copy link
Member

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.

@ignatiusmb ignatiusmb merged commit 8145f1a into master Nov 29, 2023
1 check passed
@ignatiusmb ignatiusmb deleted the lfs branch November 29, 2023 06:59
@ignatiusmb
Copy link
Member Author

Also (from https://docs.github.com/en/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage#git-lfs-objects-in-your-repository), seems like there's no way to clear the storage used by Git LFS other than to delete the whole repository

After you remove files from Git LFS, the Git LFS objects still exist on the remote storage and will continue to count toward your Git LFS storage quota.

To remove Git LFS objects from a repository, delete and recreate the repository. When you delete a repository, any associated issues, stars, and forks are also deleted. For more information, see "Deleting a repository." If you need to purge a removed object and you are unable to delete the repository, please contact support for help.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant