I work at a megacorp. We asked to pay Git folks to support monorepo sparse checkouts. They refused. Lo and behold Microsoft enters the ring, hires a Git commit

I work at a megacorp. We asked to pay Git folks to support monorepo sparse checkouts. They refused. Lo and behold Microsoft enters the ring, hires a Git committer to do it, and now it has it. Instead, we forked Mercurial, and got rid of staging and branching. Straight-line development is the way to go for most monorepos. Feature branches create a big mess. You also need sparse file systems for large mono repos otherwise the storage and network requirements exceed what is reasonable. In addition, it's imperative pushes default to running server-side sanity lints (with break-glass bypass) before accepting commits. This means either disallow pushes to production repos with a CI/CD stage + code review in-between or have some sort of proof-of-work hooks that accept local testing results. GPG has the same problem: powerful but the UX is a hot mess.