GitHub Copilot: usage metrics API now tracks pull request review phases
The GitHub Copilot usage metrics API has a new field, pull_request_review_times, which shows the median and 90th percentile duration of three pull request review phases – for enterprises and organizations with the metrics policy enabled.
GitHub has expanded the Copilot usage metrics API with a new field, pull_request_review_times, which appears in repository-level reports for enterprises and organizations (repos-1-day). The field splits the time spent in pull request review into three phases: from the moment the pull request is ready for review to the first review; from the first to the final review; and from the final review to merge. For each phase, both the median and the 90th percentile are shown in minutes, which helps distinguish typical duration from extreme cases where a small number of slow pull requests pull the overall average up.
Each record also includes information about who created the pull request and who reviewed it (in this version, only human users), and the number of pull requests merged on that day that fall under this metric. According to GitHub, this number is usually lower than the total number of merged pull requests, because it does not include those merged without any review. The phase between the first and final review shows zero if the pull request contained only one review.
Accessing the data requires the View Copilot Metrics permission and an activated Copilot usage metrics policy in the organization. The existing pull_requests field in the API remains unchanged; the new field is an addition.
Why it matters
The more detailed metric allows engineering managers to distinguish whether pull requests are delayed due to missing reviewers, repeated rounds of comments, or a forgotten merge after approval – each of these problems is solved differently. The 90th percentile also reveals when a delay is caused by just a small number of significantly slow cases, not by the entire team.
Relevant practical impact
What this means
For a business
Companies using GitHub Copilot at the enterprise or organization level can now more precisely determine where delays occur in the code review process – whether a pull request is waiting for the first reviewer, for resolution of comments between reviewers, or for the final merge after approval. This makes it possible to target process improvements at a specific phase instead of generally speeding up review.
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.