GitHub code coverage merge protection for pull requests
PreviewVerifiedAdded Sep 22, 2026
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.
Topics: Observability
Summaries of vendors' own notes. Product names and logos belong to their owners; logos via logo.dev.
More GitHub Advanced Security releases
Every GitHub Advanced Security release| Date | Release | Type |
|---|---|---|
| Jun 30 | Open source license compliance is in public preview Preview | Preview |
| Jun 30 | Dependabot no longer infers .npmrc Update | Update |
| Jun 30 | Upcoming cloud data retention policy for closed security alerts Update | Update |
| Jun 30 | Upcoming access restrictions to public API endpoints and UI views Update | Update |
| Jul 1 | Secret scanning adds validators for Asana, IBM, and MessageBird Update | Update |
| Jul 2 | Secret scanning public monitoring for enterprises Preview | Preview |
| Jun 25 | npm adds preventive account protection for high-impact accounts Update | Update |
| Jun 24 | Self-service credential revocation for incident response Update | Update |
