PR Abandon Rate
Burnout & Workflow Health
%
Unique to Projcity
Shows the percentage of pull requests closed without merging.
💡 Like tracking how many projects you start but never finish, abandoned PRs represent real time and effort that didn't ship any value.
What It Measures
Shows the percentage of pull requests closed without merging.
Why It Matters
Identifying workflow inefficiencies and wasted effort
Spotting process or planning issues (values over 30% are concerning)
How It's Calculated
Divides PRs closed without merging by total concluded PRs and multiplies by 100.
100 × COUNT(prs WHERE status = closed AND merged = false) ÷ COUNT(prs WHERE status IN (merged, closed))Concrete Example
If 12 of your 50 created PRs were closed without merging, your abandon rate is 24%, nearly 1 in 4 started pieces of work were discarded.
What Does a Healthy Score Look Like?
Lower is better, high abandon rate signals wasted effort or direction changes.
Healthy
Under 10%
Watch Out
10–25%
Needs Attention
Over 25%, significant wasted engineering effort
What Moves This Metric?
Goes up when…
Direction changes making in-progress work obsolete
PRs opened for exploration or experimentation without intent to merge
Poor upfront alignment causing rework that results in abandonment
Goes down when…
Better upfront design and alignment before coding starts
Clearer requirements reducing mid-implementation pivots
Culture of discussing approach first, coding second
Start Tracking PR Abandon 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