H.1.2 Repository Contents
Reading progress1 helpful
Prerequisites0/1 complete
Articles read
Helpful reading is optional.
Article in preparation — showing conspect notes
“One repository” does not mean every input and output belongs in Git.
- Keep human-authored source, build definitions, schemas, policy, and small reviewable fixtures when shared history matters.
- Check in generated output only for a concrete bootstrap, IDE, external-consumer, or release need; otherwise regenerate it from an owned source of truth.
- Fetch, vendor, patch, or mirror third-party source under an explicit intake and provenance policy.
- Store large binaries, datasets, models, and build products in services whose availability, access, retention, and offline behavior are operated.
- Give test data an owner, size budget, retention policy, and compatibility contract.
