[philwelch]

I bet you could address this with a third approach: metarepo. The metarepo is a repo that uses sub modules to combine your multi repo ecosystem into a simulated monorepo. The metarepo is what ultimately gets built and deployed—no versioned dependencies to manage. Local development usually happens at the multirepo level, and the metarepo is managed mostly via CI.

[amelius]

Good idea. But what gets checked in at the metarepo level? The names of the branches that are checked out in the submodules under it?

Can you have two metarepos, each with its own set of checked-out branches of the same original submodules?

[philwelch]

I believe submodules track specific branches.

[jesse_m]

Also Google's repo tool. I like the idea of manifests and the commands it includes for creating feature branches across repos