Git LFS: repo bloated to 2GB from large binaries — clones crawled
The repo bloated to gigabytes — large binaries committed directly, clones crawled. Root cause: Large files committed into Git's object store. The fix: `git lfs track` + `git lfs migrate` to move blobs out of history.
A production war story from the TheCodeForge Git series — the incident, why it happened, and the exact fix.
⏳ Timestamps:
0:00 - Cold open: 2GB .git folder
0:07 - Intro
0:16 - What Is Git LFS?
0:35 - Setup & Config
1:03 - How LFS Works
1:22 - 2GB .git folder
1:47 - Missing Git LFS tracking
2:03 - The Fix
2:22 - ⚠ Gotcha: Installing LFS after binaries already committed
2:34 - ⚠ Gotcha: CI downloads all LFS files unnecessarily
2:48 - ⚠ Gotcha: Expecting LFS files in git bisect
2:59 - Migrate Existing History with git lfs migrate
3:15 - CI/CD Selective LFS Fetch Pattern
3:36 - Production Caveat: git bisect and LFS
4:00 - Debugging Guide
4:10 - Interview Questions
4:29 - FAQ
4:46 - Key Takeaways
5:05 - Next up
5:21 - Wrap-up
👉 Full article + code: https://thecodeforge.io/devops/git-lfs/
⏭ Next up: GitHub Issues and Projects: Track Work Beyond Code
#git #devops #versioncontrol