Copilot repository-level metrics became generally available on July 17, 2026. GitHub’s usage metrics REST API can now show where Copilot coding agent and Copilot code review are active, one repository and one day at a time.

What GitHub added

Two new endpoints provide daily repository reports for organizations and enterprises:

  • GET /orgs/{org}/copilot/metrics/reports/repos-1-day?day=YYYY-MM-DD
  • GET /enterprises/{enterprise}/copilot/metrics/reports/repos-1-day?day=YYYY-MM-DD

The reports include pull requests created and merged by Copilot coding agent, plus pull requests reviewed by Copilot code review and suggestion counts by comment type. Only repositories with activity on the requested day appear in the report.

Why this matters for QA engineers

QA leaders can now separate Copilot activity by codebase instead of relying only on organization- or user-level totals. That makes it easier to compare agent adoption with repository-specific quality signals such as escaped defects, flaky-test rates, review turnaround and rollback frequency.

  • Identify repositories where AI-created or AI-reviewed pull requests need stronger test gates.
  • Target enablement where Copilot adoption is low but automation backlogs are high.
  • Build a daily governance view without exposing individual developer rankings.

Use the numbers carefully

Activity is not quality. A high number of merged agent pull requests or review suggestions does not prove better test coverage or fewer defects. Pair these metrics with CI results, defect trends and human review outcomes, and compare repositories with similar risk profiles.

Access requires the Copilot usage metrics policy to be enabled. Eligible enterprise or organization owners, billing managers and custom roles with the relevant metrics permission can retrieve the reports.

Sources