Quick Notes106 words
Scaling and optimizing a Git repository — quick notes
Scaling a repository — quick notes
| Scalar technique | Effect |
|---|---|
| Partial clone | File contents fetched on demand |
| Sparse checkout | Only the directories you work in |
| Background maintenance | Housekeeping off the critical path |
| Sharing mechanism | Nature |
|---|---|
| Package feed | Versioned, resolved by the build — preferred |
| Submodule | A commit pointer — drifts, forgotten |
| Repository resource | Check out another repo in the pipeline |
Deciding factor: does the code change together? If yes, one repo (+ Scalar). If no, split and share via packages.