Reopen Rate
Pull Request Lifecycle
%
Shows the percentage of concluded pull requests that were later reopened.
💡 Like sending an email and then having to send a follow-up correction, reopened PRs represent work that was declared done but wasn't really.
What It Measures
Shows the percentage of concluded pull requests that were later reopened.
Why It Matters
Catching instability in the review and merge process
Identifying issues with premature closure or merge decisions
How It's Calculated
Divides the count of reopened PRs by total concluded PRs (merged or closed) and multiplies by 100.
100 × COUNT(prs WHERE reopened = true) ÷ COUNT(prs WHERE status IN (merged, closed))Concrete Example
If 3 of your 50 concluded PRs were later reopened, your reopen rate is 6%, worth investigating if any pattern emerges in why they were premature.
What Does a Healthy Score Look Like?
Lower is better, reopens indicate premature closure or incorrect decisions.
Healthy
Under 2%
Watch Out
2–5%
Needs Attention
Over 5%, systemic issues with merge quality or decisions
What Moves This Metric?
Goes up when…
PRs closed to clean up the queue before being properly resolved
Merge conflicts causing reverts and reopens
Changing requirements after initial closure
Goes down when…
Clear agreement on when a PR is ready to merge
Post-merge testing catching issues before they require reopens
Better alignment on completion criteria
Start Tracking Reopen Rate
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