Commitment Reliability
Pull Request Lifecycle
%
Shows the percentage of concluded pull requests that ultimately merged.
💡 Like tracking how many of your promises you actually keep, high reliability means when you start a PR, you see it through to production.
What It Measures
Shows the percentage of concluded pull requests that ultimately merged.
Why It Matters
Tracking reliability of commitments through to completion
Understanding how often started work makes it to production
How It's Calculated
Divides the count of merged PRs by total concluded PRs (merged or closed) and multiplies by 100.
100 × COUNT(prs WHERE status = merged) ÷ COUNT(prs WHERE status IN (merged, closed))Concrete Example
If 38 of your 40 concluded PRs were merged (and 2 were closed without merging), your commitment reliability is 95%, excellent follow-through.
What Does a Healthy Score Look Like?
Higher is better, low reliability signals wasted effort or poor upfront planning.
Healthy
Over 85% of started PRs merge
Watch Out
70–85%
Needs Attention
Under 70%, significant work is abandoned before shipping
What Moves This Metric?
Goes up when…
Strong upfront alignment meaning started work is more likely to complete
Better definition of done reducing late-stage abandonment
Fewer exploratory or experimental branches
Goes down when…
Changing priorities causing work to be abandoned mid-flight
Overly complex or poorly scoped PRs being given up on
Technical blockers that prevent completion
Start Tracking Commitment Reliability
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