# Avg. Commits During PR Review

This represents the average number of commits made to each Pull Request after it is raised for review. It is an indicative measure of the quality of code & code reviews.

The average number of commits made to each Pull Request after it is raised for review. It is an indicative measure of the quality of code & code reviews.

Typo records the number of commits made to each Pull Request after they were raised for review. To calculate the final average, the total number of such commits is divided by the total number of Pull Requests raised for review within the selected time range.

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2FXnpHraUOJAHqKJ9UcspL%2FScreenshot%202025-06-23%20at%205.10.06%E2%80%AFPM.png?alt=media&#x26;token=b62c8598-20b0-4514-aee8-9b4be9a1c0c6" alt="" width="563"><figcaption></figcaption></figure></div>

> Benchmarking average commits after PR is raised provides valuable insights into code quality, code review processes, and developer productivity, enabling engineering teams to identify areas for improvement and drive efficiency gains in software development.

### **How does measuring average commits after PR is raised help in improving the Engineering teams' efficiency?**

Measuring the average number of commits after a Pull Request (PR) is raised provides valuable insights into the efficiency and effectiveness of the engineering team's development process. Here's how it helps in improving efficiency:

1. **Identifying Code Quality Issues:** A higher average number of commits after PRs may indicate code quality issues, such as incomplete or incorrect implementations.&#x20;
2. **Optimizing Code Review Processes:** Monitoring the average number of commits helps teams assess the effectiveness of their code review processes. A higher number of commits could suggest that code reviews are not thorough enough or that developers are not adequately addressing feedback before merging their changes.&#x20;
3. **Reducing Iteration Cycles:** High iteration cycles, indicated by a high average number of commits per PR, can lead to delays in the development process.&#x20;
4. **Improving Developer Collaboration:** Tracking the average number of commits fosters collaboration among team members by highlighting areas where developers may need additional support or guidance.&#x20;

