Docs
Prs Reviewed per Contributor

PRs Reviewed per Contributor

Number of Pull requests reviewed by each active contributor. Reviews can be comments or approval or request for changes. For teams, this is an average metric and for individuals this is an absolute count.

PRs-reviewed-per-contributor

Computation of the metric

  1. The version control system (eg:Git) is continously monitored for Pull Request (PR) events such as creation, updates, and closures.
  2. Review actions on PRs, including comments, approvals, and change requests, that indicate that a review has taken place are identified.
  3. Each review action is counted as one instance of PR review, regardless of the nature of the action (comment, approval, etc.).
  4. The counts are aggregated for each contributor.

Dashboards where this metric is used

  1. Dev Metric Grid

Use cases of this metric

  1. Understand how much review bandwidth does a team have
  2. Who is doing the reviews, who is not
  3. Combine with review collab dash to understand review depth & response rates
  4. Identify bottlenecks or inefficiencies in the code review process by tracking the number of PRs reviewed compared to those opened.
  5. Evaluate individual team members' contribution and effectiveness in the code review process based on the number of PRs they review.