PR Lines Removed (Avg)
Pull Request Lifecycle
lines
Shows the average lines removed per merged pull request.
💡 Like measuring how much you edit vs how much you write, some deletion is healthy, none suggests accumulating tech debt.
What It Measures
Shows the average lines removed per merged pull request.
Why It Matters
Understanding code cleanup and refactoring patterns
Monitoring how much old code is being removed per PR
How It's Calculated
Calculates the average lines removed for merged pull requests.
AVG(lines_removed WHERE pr_status = merged)Concrete Example
If your average PR removes 60 lines, you are deleting about a third as much as you add, a sign of steady code hygiene.
What Does a Healthy Score Look Like?
Some removal with each PR is healthy, zero removal suggests no cleanup.
Healthy
10–50% of added lines also removed
Watch Out
Near zero, adding without cleaning
Needs Attention
Removal exceeds additions, major rewrite territory
What Moves This Metric?
Goes up when…
Refactoring to remove duplication alongside new features
Deprecating old APIs or functionality
Consolidating modules
Goes down when…
Pure feature work without cleanup
No culture of removing old code
Large addition-only changesets like new pages or features
Start Tracking PR Lines Removed (Avg)
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