Vercel monorepos on GitHub can now emit a single consolidated commit status per pull request instead of one status per project.
Teams with large monorepos previously had to configure GitHub branch protection rules for every individual Vercel project. The new opt-in model lets you set branch protection once at the repo level, then control which specific projects are required to pass before a merge is allowed, directly from each project's Git settings.
The implementation details behind the per-project merge requirements are worth reading in full, particularly how required versus optional projects interact with the single status rollup. Enable it from your project settings under Git, and read the GitHub Commit Statuses documentation before assuming the default behavior covers your deployment topology.
[READ ORIGINAL →]