AI Launch Profile

Copilot usage metrics review-cycle fields

On July 7, 2026, GitHub added avg_pull_requests_minutes_to_review and avg_pull_requests_review_cycles fields to the totals_by_ai_adoption_phase breakdown in Copilot usage metrics.

Read official source Tool profile

At a glance

Launch Snapshot

Company: GitHub
Launch date: July 7, 2026
Launch type: Not classified
Category: AI Developer Tools
Audience: AI Platform Teams, Developers, Enterprises, Operators
Pricing: No separate public price was verified for these metrics; access is tied to eligible GitHub Copilot enterprise or organization reporting permissions and Copilot plan/billing setup.
Free plan: No
API: Yes
Open weights/source: Not publicly confirmed

Launch Context

Use these links to move from this record into the broader Launch Intelligence database.

Launch Intelligence hub Today's launches This week's launches More: AI Developer Tools

Verification & Sources

Evidence state: Recheck due
Source links: 6
Freshness: Needs recheck: checked July 8, 2026
Last updated: July 8, 2026

What this evidence state means

Definition: The claim was previously checked, but its review window expired or a material change may have invalidated it.
Required provenance: The prior evidence and check date are retained, together with the expiry or change signal that triggered recheck.
Owner: Kingy freshness queue owner and assigned editorial reviewer
Freshness rule: This is already outside its freshness rule. It must not be presented as current until reviewed against current evidence.
Disputes and corrections: Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.

Key source checks

Official site Pricing Source 1 Source 4 Source 5 Source 6

Suggest a correction

Kingy Launch Score

6.6 / 10 · Mixed

One earned credibility score, computed from cited evidence — not a placeholder. How the Kingy Launch Score works

Why this score

Source & verification 8.0/10 — The changelog, metrics reference, REST docs, interpretation guide, billing doc, and the earlier cohorts changelog — six first-party sources. github.blog
Product evidence 7.0/10 — Shipped API fields in the usage-metrics reference. docs.github.com
Significance & novelty 5.0/10 — Two review-outcome fields added to the adoption-phase breakdown — a narrow but useful reporting improvement. github.blog
Traction signals not scored — insufficient sourced evidence
Offer clarity 6.0/10 — No separate public price verified; access tied to eligible enterprise or organization reporting permissions. docs.github.com

Evidence checked 2026-07-10

Kingy AI Take

GitHub added average-minutes-to-review and review-cycle fields to the adoption-phase breakdown in Copilot usage metrics (github.blog). AI Platform Teams and Engineering Leaders measuring whether Copilot adoption correlates with faster review get two concrete downstream signals in the API. Correlation in adoption-phase aggregates is not causation, so pair these fields with your own review-process context before drawing conclusions for leadership.

Who it is for

AI Platform Teams, Developers, Enterprises, Operators

Traction notes

It gives engineering leaders more concrete downstream signals for whether Copilot adoption is associated with faster code review and fewer review loops.

Source list

Sources

Official site docs.github.com Source github.blog Source docs.github.com Source docs.github.com Source github.blog Source docs.github.com