Granular Review Stage Breakdown

According to the GitHub Changelog, enterprise and organization repository-level Copilot usage metrics reports now provide a detailed breakdown of how long pull requests spend across distinct stages of review. Teams can review the newly introduced pull_request_review_times array on each repos-1-day row to gain deeper insight into their development workflows. For more details on accessing these capabilities, developers can consult the Copilot usage metrics API documentation.

Understanding the Three Review Stages

While development teams could previously track when pull requests took an extended period to merge, identifying the precise bottleneck remained challenging. The new update splits the wait time into three distinct stages: from ready for review to the first review, from the first review to the final review, and from the final review to the merge itself. Each metric provides both a median duration and a 90th percentile measurement to highlight when a small number of unusually slow pull requests might be skewing overall delivery performance.

Data Composition and Human-Only Timing

Entries within the pull_request_review_times array record specific data points, including authored_by and reviewed_by fields alongside total_merged counts. Notably, the system times human reviews exclusively. Reviews generated by Copilot code review, other automated bots, and the pull request author are intentionally ignored during timing calculations. Consequently, the total_merged count in this array will typically fall below the figures found in standard repository-level GitHub Copilot usage metrics, which continue to count pull requests that merge without any reviews at all.

Rollout and Historical Data Constraints

Because there is no backfill mechanism for this feature, historical data will not be available. Information builds forward starting directly from the release date, meaning that reports covering the earliest days following the launch will appear relatively sparse. Furthermore, pull requests that became ready for review prior to September 21, 2026, are excluded from the review times section entirely, though they still factor into general totals.

Access and Availability

These new metrics are available directly within enterprise and organization repos-1-day reports. To view the data, users must possess appropriate permissions, such as enterprise owners, billing managers, organization owners, or individuals assigned a custom organization or enterprise role that explicitly grants the View Copilot Metrics permission. Additionally, the underlying Copilot usage metrics policy must be actively enabled.

Sources

• GitHub ChangelogUsage metrics API adds pull request review stages