Avg. to merge from first commit
The average amount of time it takes for a pull request to be merged, starting from when the first code change (commit) was made, rather than when the pull request was officially created.
Where to find it
- Health > Benchmark > Add new metric
- Health > Team Insights
Interpretation
- Low Values (< 2 hours) - indicates a very fast development and review cycle, which is positive, but could also suggest rushed work or insufficient review. Common for simple fixes or highly experienced teams. It’s important to verify code quality and review depth.
- Medium Values (2–24 hours) - reflects a healthy development pace with a solid review process. This range is typical for balanced, efficient teams and often represents the ideal balance between speed and quality. Continue monitoring for consistency and look for areas to optimize.
- High Values (> 24 hours) - extended cycles may point to complex tasks, review delays, process inefficiencies, or communication gaps. These should be investigated to identify and resolve the root causes.
Custom Dashboards
Don't forget you can anytime include any metric in your Custom Dashboards.
Updated about 24 hours ago