GitHub has updated its enterprise and organization repository-level Copilot usage metrics reporting. As reported by the GitHub Changelog, the usage metrics API now includes a breakdown of the time pull requests spend in various stages of review. Specifically, a new array called pull_request_review_times is now present on each repos-1-day row in the data.
Understanding Review Bottlenecks
Developer velocity metrics often track how long code sits awaiting review. By breaking down the specific stages of review within the repository-level Copilot usage data, engineering teams gain visibility into where pull requests may be stalling. This addition links overall coding assistant utilization metrics directly to the code review lifecycle.
What Remains Unclear
The announcement did not specify the exact definitions of each review stage included in the new array, nor did it detail whether historical data prior to this update will be backfilled to include the review time breakdowns. Further documentation from GitHub will be needed to understand how to parse the new array fields fully.
Organizations utilizing the repository-level Copilot metrics API can now begin integrating these new review stage datapoints into their internal reporting tools.
Lead image: Abdul Kayum / Pexels
