GitHub Adds Pull Request Review Stages to Copilot Usage Metrics API
GitHub has expanded its Copilot Usage Metrics API by adding a new array that measures the precise time pull requests spend in different review stages. This allows engineering teams to pinpoint specific bottlenecks in their development workflow.
GitHub has updated its Copilot Usage Metrics API at both the enterprise and organization repository levels to include detailed time breakdowns for individual pull request review stages. The newly introduced pull_request_review_times array is included in the daily repository data endpoint. It tracks and reports the duration of various phases in milliseconds, spanning from the moment a pull request is ready for review to the initial review, final approval, and eventual merge.
Primary source
Open GitHub Changelog ↗This article summarizes the source. Check the original for full details and conditions.
Comparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| Metrics granularity | Only total time to merge was tracked, making it difficult to find specific bottlenecks. | Breakdowns for review preparation, initial review, approval, and merging are available. |
| Data metrics array | Standard pull_requests field containing aggregate repository metrics. | New pull_request_review_times array added without modifying existing schemas. |
| Percentile tracking | Simple averages or overall durations for completed pull requests. | Median and 90th percentile values for each individual stage. |
Action Checklist
- Update data ingestion pipelines that consume the Copilot Usage Metrics API Ensure your parsers can handle the new pull_request_review_times array safely.
- Modify engineering dashboards to visualize the new PR stage durations Incorporate the median and 90th percentile metrics to identify active workflow bottlenecks.
- Verify API query parameters are targeting the daily repository level These metrics are packaged within the repos-1-day dataset.
