[scrubs]

@codethief Let's stipulate to all of what you write ... now per OP (to take one example) you'll need to cross the rubicon and fork git, or write your own SCS ... you're not using off the shelf.

What do you do? How do you successfully argue for the funds and time to do it then move all the poly repos into it?

Because until that's happened the problem isn't engaged in any meaningful way.

[codethief]

Why the need to fork git? It works just fine for a middle-sized company with a couple hundred devs. Let's not pretend every company is Google- or Meta-sized. Personally, I think the sweet spot for a monorepo is not a conglomerate-wide monorepo, anyway, but one at a much smaller scale where you bundle all those projects together that depend on each other but not more. There is little harm in keeping things in separate repos when they have nothing to do with each other. Yes, you might have to copy the tooling but 1) the tooling is not going to be special, 2) if you have to do the copying once or twice, that's not a big deal.