Closed LucBerge closed 1 year ago
See https://notiz.dev/blog/migrate-git-repo-to-git-lfs And https://github.com/git-lfs/git-lfs/wiki/Tutorial#migrating-existing-repository-data-to-lfs
$ git lfs migrate info --everything --include="*.d2i"
migrate: Sorting commits: ..., done.
migrate: Examining commits: 100% (309/309), done.
*.d2i 3.2 GB 71/71 files(s) 100%
$ git lfs migrate info --everything --include="*.d2o"
migrate: Sorting commits: ..., done.
migrate: Examining commits: 100% (309/309), done.
*.d2o 2.0 GB 793/793 files(s) 100%
$ git lfs migrate info --everything --include="*.swf"
migrate: Sorting commits: ..., done.
migrate: Examining commits: 100% (309/309), done.
*.swf 178 MB 23/23 files(s) 100%
Using git lfs
to manage the binary files is not enough. GitHub lfs storage is limited to 1Gb. The current usage is 3Gb with *.d2i
files.
History (or part of it) must be removed as well : https://stackoverflow.com/questions/13716658/how-to-delete-all-commit-history-in-github
Using git lfs is not a long term solution since the binary files will soon or later be bigger than 1Gb. The repo limit on GitHub is 10Gb. The best solution is to erase history for binary files when needed and not to use git lfs.
The repo size decreased from 5Gb to 1Gb.
The .git folder is growing fast: 5Gb.
Use git lfs to track: