Unreviewed PRs merged


When PRs are merged without a review, it gets counted under this metric.


Unreviewed PRs can be detrimental. From not having a feature complete releases to bug ridden releases, unreviewed PRs can negatively impact the entire process, product, and the company. The reasons why PRs are merged without reviews can range from high workloads, to large PR size, and many more.

This is an important metric to not only gauge the quality of your process but is often the reason why teams have deceptively very low cycle time. Even though low cycle time is desirable, having very low cycle time of less than a few hours is often a signal of compromise on process quality either through merging unreviewed PRs or a low quality of reviews. This metric represents the count of PRs that were merged with a review. This includes not only PRs that were not approved but also those that were not reviewed at all.

Subscribe to Hatica's blog

Get bi-weekly emails with the latest from Hatica's blog

Share this article:
Hatica logoEngineering Analytics to boost developer productivity
SOC2 monitoring powered by Vanta
GDPR monitoring powered by Vanta

Request Demo

Learn how Hatica can help you build effective engineering teams with data-driven insights

© 2019-2021 Hatica. All rights reserved.