I think GitHub/Gitlab (enterprise or public), do an excellent job of capturing the monorepo desires, but with lots of disparate code repositories. That is, mon

I think GitHub/Gitlab (enterprise or public), do an excellent job of capturing the monorepo desires, but with lots of disparate code repositories. That is, mono repos are great for single company wide access, easy to fork and commit against different areas, have a single system for driving all CI changes across repos. I agree that having a single huge repo kinda sucks in Git, but it's also basically a nonstarter for companies that want all the features of git, but their repo and build is monolithic. Would you require people to first completely rebuild their software into separate Git repos before using Git? This could take years! I've been looking at this exact problem at my work, and there is no easy answer here. I think MS probably picked the easier path forward in their case.