Practise the vocabulary of repository structure decisions: monorepo, polyrepo, coupling trade-offs, ownership, and migration language.
0 / 5 completed
1 / 5
A ___ stores all projects and packages for an organisation in a single version-controlled repository.
A monorepo (monolithic repository) contains all related projects, packages, and services in one repository. Google, Meta, and Shopify use monorepos to enable atomic cross-project changes.
2 / 5
In a monorepo, ___ defines which team owns which files or packages, often enforced via a CODEOWNERS file.
Code ownership maps teams to the packages, directories, or files they maintain. A CODEOWNERS file in GitHub/GitLab automatically assigns reviewers based on which files are changed.
3 / 5
A key advantage of a monorepo is the ability to make ___ changes across multiple packages in a single commit.
Atomic changes — modifying multiple packages in a single commit — are a core monorepo advantage. In polyrepos, the same change requires coordinated PRs across multiple repositories.
4 / 5
'At Google scale, a monorepo requires specialised ___ tooling to keep build times acceptable' — which word fits?
Specialised build tooling (Bazel, Pants, Buck) is needed at scale to make monorepos practical. Without incremental builds and remote caching, CI times become prohibitive.
5 / 5
Moving from multiple separate repositories into a single monorepo is called ___ the repositories.
Repository consolidation is the process of merging polyrepos into a monorepo, typically using tools like git-filter-repo to preserve history.