…anch as a single unit but are too large to fit into one reasonable CR, consider a stacked CR model: Create a primary branch
feature/big-feature and a number of secondary branches (e.g.,
feature/big-feature-testing, etc.) that each encapsulate a subset of the functionality and that get individually code-reviewed against the
feature/big-feature branch. Once all secondary branches are merged into
feature/big-feature, create a CR for merging the latter into the main branch.
Why did I not think of this?!? So obvious…