GitHub Copilot Usage Metrics Now Break Down Pull Request Review Timing
GitHub’s enterprise and organization repository-level Copilot usage metrics reports now break down how long pull requests spend in each stage of the review process.
Details
- New field: a
pull_request_review_timesarray reporting median and 90th-percentile durations for three phases — ready for review to first review, first review to final review, and final review to merge - What it reveals: whether pull requests are bottlenecked waiting for initial reviewer attention, caught in back-and-forth discussion cycles, or stalled after approval before merging
- Who can access it: enterprise owners, billing managers, organization owners, and users with a custom role granting “View Copilot Metrics” permission, provided the usage metrics policy is enabled
What happened next
The breakdown gives organizations a way to diagnose exactly where in the review pipeline delays are happening, rather than only seeing an aggregate time-to-merge figure.