H.3.1 Git Workspace

recommended
Reading progress1 helpful
Article in preparation — showing conspect notes

Large repositories stress independent Git dimensions rather than one generic notion of size.

  • Partial clone changes object transfer; sparse checkout changes populated paths; shallow history removes ancestry.
  • Evaluate later fetches, blame, merge-base, bisect, generators, IDEs, and discovery before narrowing a workspace.
  • Commit graphs, filesystem monitoring, multi-pack indexes, and background maintenance target local interactive costs.
  • Compare cold and warm behavior, on-demand fetch, disk use, failure recovery, and context-switch cost by cohort.
  • Mirrors and snapshots are repository services, not merely local Git flags.