llm-wiki/raw/articles/github-code-coverage-merge-protection-2026.md

source_url, ingested, sha256, discovered_from

source_url	ingested	sha256	discovered_from
https://github.blog/changelog/2026-06-30-github-code-coverage-merge-protection-for-pull-requests/	2026-06-30	f8c59185ef1c13039240478afb5f7184b4b7e06f418fe1069b2ac223cae294e3	platform channel_id channel_name message_id author_id posted_at message_excerpt discord 1028287639918497822 chat 1521584553565753536 890908900520505354 2026-06-30T18:33:47.244000000Z Direct #chat link to GitHub code coverage merge protection changelog.

Back to changelog

You can now use branch rulesets to block pull requests from merging when test coverage drops below thresholds you set.

You can set a minimum coverage percentage, a maximum allowed drop from the default branch, or both. You can start in evaluate mode to understand impact first, then switch to active mode when you’re ready to enforce merge protection.

This gives your team a practical quality gate at merge time so you can reduce accidental regressions and keep testing standards consistent as code changes.

This feature is now in public preview for all GitHub Code Quality users on github.com. GitHub Code Quality is available today for GitHub Enterprise Cloud and Team, but isn’t yet available on GitHub Enterprise Server. It’s free during the preview period.

Learn more

• Learn more about Code coverage in our documentation.
• Check out our GitHub Code Quality documentation.
• Join the discussion and leave feedback on the Code Coverage announcement in the GitHub Community.