Comments per PR
Pull Request Lifecycle
comments
Shows the average number of comments received on your authored pull requests.
💡 Like the number of sticky notes your editor leaves on your manuscript, too few means no engagement, too many might mean the draft needed more polish.
What It Measures
Shows the average number of comments received on your authored pull requests.
Why It Matters
Understanding review engagement and feedback volume
Gauging how much discussion your PRs generate
How It's Calculated
Divides total comments received on your PRs by the number of authored PRs.
AVG(comments_count WHERE pr_author = user)Concrete Example
If your PRs average 4 comments each, reviewers are engaged and giving useful feedback, that is a healthy conversation level.
What Does a Healthy Score Look Like?
Aim for a healthy conversation, neither too sparse nor overwhelmingly critical.
Healthy
2–8 comments per PR
Watch Out
Over 15 comments per PR consistently
Needs Attention
Near zero (no review engagement) or over 20 (significant issues)
What Moves This Metric?
Goes up when…
Large PRs generating more feedback from reviewers
Code quality issues triggering thorough reviews
Reviewer culture encouraging detailed comments
Goes down when…
Smaller PRs with a clearer scope reducing review surface area
Higher code quality reducing the need for comments
Reviewers approving without detailed feedback
Start Tracking Comments per PR
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