PRs Merged Without Review
Pull Request Lifecycle
Counts the number of merged pull requests that had no review or approval.
💡 Like food leaving the kitchen without a quality check, most of the time it is fine, but the risk is much higher.
What It Measures
Counts the number of merged pull requests that had no review or approval.
Why It Matters
Identifying code that shipped without peer review
Monitoring compliance with review requirements
How It's Calculated
Counts merged PRs with no review actions or approvals in the date range.
COUNT(prs WHERE status = merged AND review_count = 0)Concrete Example
If 5 PRs were merged without review this sprint, that is 5 changes that bypassed your quality gate, worth understanding if intentional or accidental.
What Does a Healthy Score Look Like?
Lower is better, unreviewed merges represent process risk.
Healthy
0 per sprint
Watch Out
1–3 per sprint (hotfixes or bot PRs)
Needs Attention
More than 5, systemic bypass of review process
What Moves This Metric?
Goes up when…
Emergency hotfixes bypassing normal process
Bot or automated PRs merged without review
Culture of merging own PRs under deadline pressure
Goes down when…
Branch protection rules requiring at least one approval before merge
Explicit hotfix process with post-merge review
CI/CD enforcement of review requirements
Start Tracking PRs Merged Without Review
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com