Practise vocabulary for planning and communicating a migration from polyrepo to monorepo: consolidation, cut-over, risk communication, and team coordination.
0 / 5 completed
1 / 5
The process of moving multiple separate repositories into a single monorepo is called ___ consolidation.
Repository consolidation is the process of merging polyrepos into a monorepo. Tools like git-filter-repo and git subtree help migrate history while preserving commit authorship.
2 / 5
During a monorepo migration, a ___ period prevents new features from being merged to the old repositories while the migration is in progress.
A freeze period (also called a code freeze or merge freeze) pauses new commits to the source repositories during migration to prevent conflicts and ensure a clean, complete import.
3 / 5
The ___ date is the planned moment when teams switch from the old polyrepo structure to the new monorepo for all development work.
The cut-over (or go-live) date marks the switch to the new monorepo. Teams need to update their local clones, CI configurations, and CODEOWNERS assignments after this date.
4 / 5
A key risk to communicate in a monorepo migration plan is ___ during initial CI runs as caches are empty and all packages rebuild.
Initial CI runs in a new monorepo are slow because the build cache is empty. Teams should expect and communicate this 'cold cache' period and plan for gradual cache warming.
5 / 5
`git filter-repo` is a tool used during monorepo migration to ___.
git filter-repo rewrites git history, enabling teams to import code from a polyrepo into a monorepo subdirectory while preserving the full commit history, authors, and timestamps.