Thoroughly reviewed PRs

Tags: Flow

Thoroughly reviewed PRs is the percentage of merged pull requests that have at least one regular or robust non-excluded, non-submitter comment, rounded to the nearest tenth of a percent.

Which reports use Thoroughly reviewed PRs?

Check out Thoroughly reviewed PRs in Team health insights, Review collaboration, and Check-in.

back to top

What does Thoroughly reviewed PRs measure?

The Thoroughly reviewed PRs metrics helps you ensure your teams’ PRs are being thoroughly reviewed.

Thorough comments relate positively to code review quality and healthy team collaboration. Too many pull requests merged without thorough review could be a sign of rubber-stamping during the code review process.

Use this metric in conjunction with Unreviewed PRs. Use Unreviewed PRs to check if there’s any review for your PRs, and check it against Thoroughly reviewed PRs to see if that review is substantial.

back to top

How is Thoroughly reviewed PRs calculated?

A thoroughly reviewed PR is one that has at least one regular or robust non-excluded, non-submitter comment.

Note: The settings for trivial, regular, and robust comments are configurable by plan. Learn more about configuring comment robustness.

Thoroughly reviewed PRs is calculated as the total number of thoroughly reviewed merged pull requests an individual, team, or organization was involved in, divided by the total number of merged pull requests the individual, team, or organization was involved in.

A user is involved in a pull request if they comment on or approve the pull request, even if their comment is not regular or robust.

Note: Approvals do not count as regular or robust comments.

back to top

What data is included in Thoroughly reviewed PRs?

A pull request counts toward Thoroughly reviewed PRs if it is a merged pull request.

Pull requests are not counted toward PR iteration time if:

  • they are created by a user who is excluded from reports
  • they are created by a hidden user
  • they are an excluded pull request
  • they are from a deleted repository

Note: User view rights and permissions also impact how specific users will see PR iteration time.

back to top

If you need help, please contact Pluralsight Support.