PR Throughput / Day
Pull Request Lifecycle
pr / business day
Shows the average number of pull requests merged per weekday.
💡 Like your delivery van's daily shipments, throughput per day tells you the rate at which code is flowing from development to production.
What It Measures
Shows the average number of pull requests merged per weekday.
Why It Matters
Tracking review-and-merge cadence
Understanding delivery velocity for code changes
How It's Calculated
Calculates the average of 1 divided by weekdays between first commit and merge for merged pull requests.
AVG(1 ÷ business_days(first_commit, merged_at) WHERE pr_status = merged)Concrete Example
If your team is merging 0.8 PRs per business day on average, you are delivering roughly 4 PRs per week, one per developer for a 5-person team.
What Does a Healthy Score Look Like?
Higher is better, more frequent merges mean smaller changes and less risk.
Healthy
0.5–2 merges per business day per developer
Watch Out
Under 0.2 per developer per day
Needs Attention
Near zero, code is sitting in PRs, not shipping
What Moves This Metric?
Goes up when…
Fast review cycles allowing PRs to merge quickly
Smaller PRs that are easy to review and approve
Continuous integration culture with daily shipping habits
Goes down when…
Large PRs that sit in review for days before merging
Slow reviewer response times blocking progress
Complex approval requirements adding friction
Start Tracking PR Throughput / Day
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