Pull Requests Merged
Activity Volume
Counts the number of your pull requests that were merged during the selected period.
💡 Like a pipeline completing a batch, each merge is finished work that's ready for users.
What It Measures
Counts the number of your pull requests that were merged during the selected period.
Why It Matters
Tracking how much reviewed work actually ships to production
Measuring successful completion of code contributions
How It's Calculated
Counts each pull request merge event in the date range.
COUNT(pr_merge_events WHERE timestamp BETWEEN measure_from AND measure_to)Concrete Example
If you merged 12 pull requests in a two-week sprint, that's 6 merges per week, meaning code is flowing steadily to production.
What Does a Healthy Score Look Like?
Higher is better, merged PRs represent shipped value.
Healthy
4–10 merges per week
Watch Out
1–3 merges per week
Needs Attention
Zero merges over multiple days
What Moves This Metric?
Goes up when…
Fast reviewer response and approval cycles
Smaller PRs that are easier and quicker to review
Automated CI checks that catch issues early
Goes down when…
Large PRs requiring extensive review time
Review bottlenecks or waiting on specific reviewers
Merge conflicts or failing CI pipelines blocking completion
Start Tracking Pull Requests Merged
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