How I diagnosed and fixed a 486MB git repo where the actual code was only 6MB. Finding bloat, rewriting history, and choosing between Git LFS and compression.
High Performance Git
High Performance Git by Ted Nyman, a book about Git internals and large Git repositories.
The Git Commands I Run Before Reading Any Code
Five git commands that tell you where a codebase hurts before you open a single file. Churn hotspots, bus factor, bug clusters, and crisis patterns.
git fetch する度に"Auto packing the repository in background for optimum performance." が出る - Qiita
1年ぐらい毎日コミットし続けているディレクトリの話 Auto packing the repository in background for optimum performance. See "git help gc" for manual housekeeping. ...
Everyone is doing Git on S3 wrong
Why Git is hard to put on object storage, where write-ahead logs fall short, and how Enroute reaches 7,600+ pushes per second on a single repository.
Gregory Szorc's Digital Home | High-level Problems with Git and How to Fix Them
When Git first came onto the scene in the mid 2000's, I was initially skeptical because of its horrible user interface. But once I learned it, I appreciated its speed and features - especially the ease at which you could create feature branches, merge, and even create commits offline (which was a big deal in the era when Subversion was the dominant version control tool in open source and you needed to speak with a server in order to commit code). When I started using Git day-to-day, it was such an obvious improvement over what I was using before (mainly Subversion and even CVS).
How we built Git storage for millions of Netlify projects
A technical look at how Netlify built Netlify Source: durable Git storage on S3, scalable caching, push consistency, and support for millions of projects.
A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING GIT ADD OR GIT COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime Git teacher and GitHub evangelist, taking the tool apart down to https://t.co/vJNRCmSBb9
A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING GIT ADD OR GIT COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED55 minutes from Tim Berglund, a longtime Git teacher and GitHub evangelist, taking the tool apart down to… https://t.co/z8Tf4udInA pic.twitter.com/vJNRCmSBb9— slash1s (@slash1sol) June 4, 2026
Git at any scale · Cursor
Hosting Git repositories at scale is a nightmare. When Linus Torvalds designed the first version of the information manager from hell (that's actually the tagline for Git, look it up), he had a very specific use case in mind: his own. He wanted to replace BitKeeper, the distributed version control system that was being used to develop the Linux Kernel. Of course, the replacement had to be distributed too. The Kernel is an unusual software project; it is extremely decentralized, with many different maintainers for its many different subsystems. A distributed version control system is a natural fit for this workflow.
Code Repository - Git Source Control | Harness
Host Git repositories in Harness, manage pull requests, and connect every commit to secure CI/CD workflows with source-to-deploy traceability.
Introducing git-wt: Worktrees Simplified
In my previous post, I explained why the bare repo pattern makes git worktrees actually pleasant to use. But setting it up manually requires 10+ commands. And t...
