Git at Scale
summary
Explains how Microsoft moves massive repos into Git and what actually changes: supports a 270 GB Windows mono‑repo with ~4,000 daily developers by using Git LFS for large binaries, a server merge queue to serialize simultaneous pull‑request merges, and the virtual filesystem VFS for Git to make clones fast and on‑demand. Clone time drops from hours to ~90 seconds, git status to ~8 seconds, and add/commit to ~5s each. Also optimizes Git for Windows by converting slow shell scripts (rebase, stash) into C built‑ins.
AI-written summary · about
chapters (5)
- 0:00Start
- 16:47Code Integration Azure Repos uses a merge queue' for Pull Requests
- 21:38Azure Pipelines
- 29:35Large Files Multiple versions of large binary files
- 47:37Limitations of VFS for Git Must be online the first time you open a file Only it works with VFS for Git repositories








