Avg. to merge from first review
The average amount of time (in seconds) that pull requests take from when they receive their first review until they are successfully merged into the main codebase.
Where to find it
- Delivery > PR Insights > Review Time
- Health > Benchmark > Add new metric
- Health > Team Insights > Add new metric
Interpretation
Larger companies
-
High: Less than 24 hours - show fast incorporation of first-review feedback and merge readiness. Typically reflects small, well-scoped PRs, green CI, clear code ownership, and “merge-when-green”/auto-merge practices, often supported by feature flags. Watchouts: superficial fixes or skipping deeper tests—use required checks and spot audits.
-
Medium: Between 24 and 72 hours - a healthy enterprise norm that allows time to address comments, rerun CI, complete security/licensing scans, and align across time zones/approvers. Signals solid process: clear “blockers vs. nits,” responsive authors/reviewers, and stable pipelines. Maintain by keeping PRs small, using checklists, and setting SLAs for follow-ups.
-
Low: More than 72 hours - indicates post-review bottlenecks: large rework, unclear acceptance criteria, flaky/slow CI, scarce approvers, cross-team dependencies, or coupling to release windows/freeze periods. Improve by splitting PRs, tightening which checks are truly blocking, enabling non-blocking follow-up PRs, widening code-owner backups, scheduling merge windows, and stabilizing tests.
Smaller companies
- High: Less than 2 hours - indicate a very fast response to feedback and quick merges, which can be positive, but may also suggest rushed handling or lack of proper iteration. It’s important to ensure feedback is being thoughtfully addressed, not just quickly dismissed.
- Medium: Between 2 and 8 hours - represent a healthy timeframe for addressing feedback and completing reviews. This range is typical for effective teams with strong communication. Consistency should be monitored to maintain quality.
- Low: More than 8 hours - suggest slow feedback response, possibly due to developer availability, complex required changes, communication delays, or process inefficiencies. These areas may need improvement.
Custom Dashboards
Don't forget you can anytime include any metric in your Custom Dashboards.
Updated 10 days ago