Unreviewed PRs merged
Number of PRs that were merged without having their first review.
App inputs to this metric:
GIT/VCS tools
Use cases:
-
Having unreviewed PRs merged can be an indication of poor code practices.
-
Unreviewed PRs have higher probability of introducing bugs in production, thus increasing your change failure rate
-
Unreviewed PRs can also indicate a lack of expertise in the team to review a complex PR
-
Higher size of PR might lead to longer pick up times, and sometimes even PRs being merged without review
Some more references:
https://www.hatica.io/blog/code-review-practices/ (opens in a new tab)