PR Lines Added (Avg)
Pull Request Lifecycle
lines
Shows the average lines added per merged pull request.
💡 Like the average length of your emails, useful for knowing whether your communication style is concise or verbose.
What It Measures
Shows the average lines added per merged pull request.
Why It Matters
Understanding how much new code is being introduced per PR
Monitoring code growth patterns
How It's Calculated
Calculates the average lines added for merged pull requests.
AVG(lines_added WHERE pr_status = merged)Concrete Example
If your average PR adds 180 lines, reviewers can typically absorb under 200 lines of new code in a single review session.
What Does a Healthy Score Look Like?
Lower is better, smaller additions per PR are easier to review.
Healthy
Under 150 lines added per PR
Watch Out
150–400 lines added per PR
Needs Attention
Over 400 lines, additions are too large per PR
What Moves This Metric?
Goes up when…
Large features shipped in single PRs without decomposition
New modules or services introduced all at once
Test suites added in bulk
Goes down when…
Breaking feature work into smaller incremental PRs
Adding tests alongside code rather than in batches
Using feature flags to deliver code in pieces
Start Tracking PR Lines Added (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