# Unreviewed PRs

<figure><img src="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2FzoCskm6csRVbD8RKh0ae%2FScreenshot%202025-11-28%20at%2012.28.49%E2%80%AFPM.png?alt=media&#x26;token=71d7b643-edc1-401e-9f4f-6bf7233c5068" alt="" width="563"><figcaption></figcaption></figure>

#### All merged PRs that do not have a review state are PRs merged without review.&#x20;

* Reviewing every PR saves a lot of post-production issues and can keep higher quality across.
* Merging PRs without review is a symptom of production issues or poor-quality code that could lead to higher maintenance issues in the future. Also, junior engineers miss out on learning opportunities.

#### Industry Benchmarking

<figure><img src="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2FHcUOpTST4yG3BaJlk5ON%2Fimage.png?alt=media&#x26;token=a7463288-0cc6-4847-972f-5d975c75fc6e" alt="" width="563"><figcaption></figcaption></figure>

#### Related article

{% content-ref url="../../improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage" %}
[best-practices-for-ensuring-strong-pull-request-review-coverage](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage)
{% endcontent-ref %}

{% content-ref url="../../improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review" %}
[best-practices-for-team-ownership-in-code-review](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review)
{% endcontent-ref %}