Git at Scale
|
Note
|
Draft placeholder — outline notes only; prose not yet written. |
Points this chapter’s introduction needs to make:
-
Why big repositories and big teams strain Git: history size, object count, working-tree size, ref count
-
A map of the scaling toolbox and how the pieces relate: shallow clones, partial clones, sparse checkout, Scalar, background maintenance, large-file storage, and monorepo practices
-
Where the on-disk format details live (Ch 10, Git Internals) versus the day-to-day operations covered here
Shallow Clones
|
Note
|
Draft placeholder — outline notes only; prose not yet written. |
Points this section needs to cover:
-
git clone --depth,--shallow-since,--shallow-exclude -
Deepening and unshallowing:
git fetch --deepen,--unshallow -
--no-tagsto avoid tag bloat -
CI patterns: fast single-revision checkouts
-
Limitations: no full history for
log/blame/bisect, server cost of shallow negotiation — why partial clone is often the better tool