PR Size (Lines)
Pull Request Lifecycle
lines
Shows the average total lines changed per merged pull request.
💡 Like the word count of a document you're asked to proofread, there is a readable sweet spot beyond which quality suffers.
What It Measures
Shows the average total lines changed per merged pull request.
Why It Matters
Understanding typical PR scope and reviewability
Monitoring if PRs are getting too large for effective review
How It's Calculated
Calculates the average lines changed (added + removed) for merged pull requests.
AVG(lines_added + lines_removed WHERE pr_status = merged)Concrete Example
If your average PR changes 250 lines (added + removed), reviewers are processing a reasonable amount of code per review session.
What Does a Healthy Score Look Like?
Lower is better, smaller PRs are easier to review thoroughly.
Healthy
Under 200 lines changed
Watch Out
200–500 lines changed
Needs Attention
Over 500 lines. PRs are too large for high-quality reviews
What Moves This Metric?
Goes up when…
Large feature implementations being shipped in single PRs
Limited decomposition of work
Infrastructure changes touching many files at once
Goes down when…
Deliberate PR decomposition breaking features into smaller pieces
Using feature flags to enable incremental delivery
Separating test changes from implementation changes
Start Tracking PR Size (Lines)
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