SYSTEM Cited by 3 sources

Git

Git is the dominant distributed version control system (origin: Linus Torvalds, 2005). Data model: a content-addressed object store (blobs / trees / commits / tags keyed by SHA-1/SHA-256) rooted in .git/objects/, plus refs (branches, tags) pointing at commit objects.

Runtime concerns that matter at scale in the wiki:

• Storage layout. Loose objects first (one file per object), then repacked into pack files (.pack + .idx) for compact on-disk representation; pack files are where delta compression happens.
• Transfer. git clone / git fetch / git push move pack files, not loose objects; a server typically rebuilds the transfer pack dynamically per request from what the client already has (the source of why local repack improvements don't survive a server-mediated round trip — see systems/github).
• Repack. git repack -adf (-a all-in-one, -d delete replaced, -f refuse delta reuse) + --window=N (how many nearby objects to consider as delta candidates) + --depth=N (max delta chain length) are the knobs that make aggressive compression possible; defaults are tuned for average repos, not for pathological structural mismatches.
• Pluggable signing. gpg.format=openpgp|ssh|x509 + gpg.x509.program=<signer> let organisations plug GPG / SSH / or S/MIME (X.509) signers into the commit-signing path — see concepts/commit-signing and the Figma device-trust system.

Defaults that matter

• Delta pairing heuristic: Git pairs files for delta compression using only the last 16 characters of the file path. Works for typical codebases where similar names usually mean similar content; can go pathological when the distinguishing portion of the path falls outside those 16 characters (Dropbox i18n canonical instance — see concepts/git-delta-compression and sources/2026-03-25-dropbox-reducing-monorepo-size-developer-velocity).
• Repack window / depth defaults (--window=10 --depth=50 on git gc) are conservative; tuned values like --window=250 --depth=250 trade time for compression ratio.
• --path-walk flag: experimental option that walks the full directory tree for delta-candidate selection instead of using the 16-char heuristic; effective on structurally-mismatched repos but incompatible with GitHub's server-side bitmap / delta-island optimizations.

Stub page

This page exists because Git internals became load-bearing in a wiki source and we need a canonical anchor. Most Git behaviour is out of scope here; see concepts/git-pack-file and concepts/git-delta-compression for the aspects the wiki covers.

Seen in

• sources/2026-03-25-dropbox-reducing-monorepo-size-developer-velocity — Dropbox traces 87 GB monorepo growth to Git's 16-char path heuristic pairing .po files across languages; fixes via a tuned server-side repack at 84 GB → 20 GB.
• sources/2025-09-15-github-post-quantum-security-for-ssh-access-on-github — Git-over-SSH is the transport getting PQ-KEX (sntrup761x25519-sha512) on github.com's SSH endpoints as of 2025-09-17. Git-over-HTTPS unaffected; independent crypto-agility timelines per transport.
• sources/2026-04-16-cloudflare-artifacts-versioned-storage-that-speaks-git — Git's smart-HTTP protocol + object graph reused as the wire protocol of a generic versioned-storage primitive (Cloudflare Artifacts). Canonical wiki instance of patterns/git-protocol-as-api: Git chosen specifically because "it's deep in the training data of most models" and sidesteps the bootstrap problem of a new protocol. Server is a ~100 KB pure-Zig Wasm Git server running inside Durable Objects — first wiki instance of a complete Git server reimplemented in Wasm (SHA-1, zlib, delta encode/decode, pack parsing, smart-HTTP v1+v2 from scratch). Artifacts also makes .import() + .fork() first-class alongside clone / fetch / push and natively supports git-notes for agent-written metadata. Sibling ArtifactFS exploits Git's partial-clone (--filter=blob:none) machinery for blobless-clone + async-hydration on any Git remote.

Related

• concepts/git-pack-file — Git's compressed object format.
• concepts/git-delta-compression — the 16-char heuristic failure mode.
• patterns/server-side-git-repack — tuned repack as the platform-compatible fix shape.
• concepts/commit-signing — pluggable signer interface.
• concepts/wasm-git-server — Cloudflare Artifacts' ~100 KB pure-Zig Wasm reimplementation of the Git smart-HTTP server.
• concepts/async-clone-hydration — ArtifactFS' blobless-clone + background-hydration treatment of Git's partial-clone machinery.
• concepts/repo-per-agent-session — Git-repo-as-agent-state substrate (Cloudflare internal-dogfood pattern on Artifacts).
• patterns/git-protocol-as-api — Git as the wire protocol of an agent-first storage primitive.
• patterns/blobless-clone-lazy-hydrate — startup-latency pattern for large-repo agent sandboxes.
• patterns/do-backed-git-server — per-repo actor + Wasm engine substrate.
• systems/cloudflare-artifacts — canonical instance of Git-protocol-as-API for an agent-first storage primitive.
• systems/artifact-fs — client-side FS driver for blobless-clone + lazy hydration.
• systems/github — the managed-SaaS layer on top of Git where server-side pack construction lives.