Usage metrics API adds pull request review stages
Summary
The enterprise and organization repository-level Copilot usage metrics reports now break down how long pull requests spend in each stage of review. A new pull_request_review_times array on each repos-1-day row… The post Usage metrics API adds pull request review stages appeared first on The GitHub Blog .
Original Text
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> The enterprise and organization repository-level Copilot usage metrics reports now break down how long pull requests spend in each stage of review. A new pull_request_review_times array on each repos-1-day row reports a median and a 90th percentile for the time from ready for review to first review, first review to final review, and final review to merge.
What’s new
Each entry in pull_request_review_times includes:
authored_by and reviewed_by: Who opened and who reviewed the pull requests in this entry. Both are human in this release.
total_merged: The number of qualifying pull requests merged in the repository that day.
median_minutes_ready_to_first_review and p90_minutes_ready_to_first_review: Time from the pull request becoming ready for review to its first review.
median_minutes_first_to_final_review and p90_minutes_first_to_final_review: Time between the first and final review.
median_minutes_final_review_to_merge and p90_minutes_final_review_to_merge: Time from the final review to merge.
Durations are in minutes and attributed to the day the pull request merged. The existing pull_requests fields are unchanged.
Why this matters
Teams can already see when pull requests take a long time to merge, but not where the time goes. Splitting the wait into three stages shows whether a pull request is waiting for someone to look at it, waiting on back-and-forth between reviewers, or sitting approved and unmerged. Each of those points to a different fix, and the 90th percentile beside the median shows when a handful of slow pull requests is driving the delay.
Important notes
Availability: Present in the enterprise and organization repos-1-day reports.
What is counted: Pull requests that a person opened and at least one other person reviewed. Only human reviews are timed. Reviews from Copilot code review, other bots, and the author are ignored, so a pull request reviewed by both a person and Copilot code review is still included. As a result, pull_request_review_times[].total_merged is usually lower than pull_requests.total_merged, which also counts pull requests merged without any reviews.
No backfill: Data builds forward from the release date, so early days will be thin. Pull requests that became ready for review before September 21, 2026 are left out of this section but still count toward pull_requests.total_merged.
A quiet day is an empty array, not a zero: The array is [] on days a repository merged no qualifying pull requests. The first-to-final review stage is 0 when pull requests receive a single review.
Access: Enterprise owners and billing managers, organization owners, and anyone with a custom organization or enterprise role that grants the View Copilot Metrics permission can access these reports. The Copilot usage metrics policy must be enabled.
Visit the Copilot usage metrics API documentation to get started.
The post Usage metrics API adds pull request review stages appeared first on The GitHub Blog.
Lotu Radar provides attributed news summaries and links to the original publisher. Full reporting and copyright remain with the source.