PR Lines Removed
Pull Request Lifecycle
lines
Shows the total lines removed across all merged pull requests.
💡 Like pruning a tree, healthy codebases regularly remove dead code, old features, and unnecessary complexity.
What It Measures
Shows the total lines removed across all merged pull requests.
Why It Matters
Tracking code cleanup and refactoring effort
Understanding overall code removal volume
How It's Calculated
Sums all lines removed in merged pull requests in the date range.
SUM(lines_removed WHERE pr_status = merged)Concrete Example
If your team removed 2,000 lines this week while adding 5,000, you are growing the codebase by 3,000 net lines, track this ratio over time.
What Does a Healthy Score Look Like?
Higher removals are often healthy, it means code is being cleaned up.
Healthy
Removals are 30–50% of additions
Watch Out
Near zero removals (code only grows)
Needs Attention
Extremely high removals may signal major rewrites
What Moves This Metric?
Goes up when…
Refactoring and dead code cleanup being prioritised
Feature deprecation removing old code paths
Dependency upgrades replacing verbose boilerplate
Goes down when…
Pure feature delivery periods adding code without cleanup
Low refactoring culture
Fear of removing code that might be needed again
Start Tracking PR Lines Removed
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