Pull Requests Created
Activity Volume
Counts the number of pull requests you opened during the selected period.
💡 Think of each PR as a delivery box, you're packaging up your work for teammates to inspect and approve.
What It Measures
Counts the number of pull requests you opened during the selected period.
Why It Matters
Gauging how many changes you are preparing for review
Tracking your code contribution pace
How It's Calculated
Counts each pull request creation event in the date range.
COUNT(pr_creation_events WHERE timestamp BETWEEN measure_from AND measure_to)Concrete Example
If you opened 8 pull requests in a two-week sprint, you averaged 4 per week, a healthy contribution pace.
What Does a Healthy Score Look Like?
More PRs usually means smaller, safer changes, easier to review and merge.
Healthy
4–10 PRs per week
Watch Out
1–3 PRs per week
Needs Attention
Zero PRs over multiple days
What Moves This Metric?
Goes up when…
Breaking work into smaller, more focused changes
Faster development pace and frequent commits
Feature flags enabling more frequent partial shipping
Goes down when…
Large monolithic changes being batched into one PR
Blocked by dependencies or review backlog
Low-activity periods such as planning sprints or vacation
Start Tracking Pull Requests Created
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