← Back
GitHub
GitHub expands Copilot Usage Metrics API with org-level pull request throughput parity
GitHub Copilot · apifeaturerelease · github.blog ↗

Overview

GitHub is expanding the organization-level Copilot Usage Metrics API to include a comprehensive set of pull request activity metrics. This update brings organization-level endpoints to feature parity with what was previously available only at the enterprise level, enabling standardized reporting and deeper visibility into Copilot's impact on development workflows.

What's New

Organizations can now retrieve daily aggregated pull request activity and Copilot participation metrics directly from the org-level API, including:

Baseline Pull Request Activity:

  • Total pull requests created, reviewed, and merged
  • Median time to merge (in minutes)

Copilot Participation Metrics:

  • Pull requests created by Copilot coding agent
  • Pull requests reviewed by Copilot code review
  • Review suggestions and applied suggestions counts
  • Copilot-created pull requests that were merged
  • Median time to merge for Copilot-created pull requests

Why This Matters

With this update, engineering teams and organizations can:

  • Standardize reporting across the organization using a single API
  • Quantify Copilot's impact on the entire pull request lifecycle, from creation through merge
  • Track actionable feedback by monitoring not just suggestion volume but also applied suggestions
  • Improve visibility into non-IDE Copilot usage, including agent-created pull requests and Copilot code review activity

Important Considerations

Organizations should note a few key points when using these metrics:

  • Multi-org users: If your organization belongs to an enterprise, organization-level totals may not match enterprise totals, since users can belong to multiple organizations (creating duplicate counting in org reports that enterprise reporting deduplicates)
  • Empty IDE data: If the API shows empty results for everything except pull request data, the organization likely lacks IDE usage and only has pull request data available
  • Repository transfers: Repo transfers can split attribution. If a repository is transferred after a PR is created but before it's merged, events may be attributed to different organizations

Developers integrating with this API should consult the official Copilot usage metrics documentation for complete field definitions.