Summary
On October 8, 2026, GitHub gave organizations new controls over Copilot code review: owners can choose whether reviews bill a member's own Copilot quota or the organization that owns the repository (with optional budgets via AI Credits), and can restrict who may trigger reviews to authorized, org-provided licenses.
What changed
GitHub added a 'Choose how members with a Copilot license are billed' setting for Copilot code review (default bills the member's quota; the alternative bills the repository-owning organization and requires AI Credits paid usage with an optional budget) and an 'Only allow Copilot code review to be triggered by authorized users' setting that blocks requests from external licenses, enforceable org-wide.
Why it matters
Granular billing and trigger controls let organizations stop individual quotas from being exhausted, cap AI review spend, and restrict who can invoke paid AI reviews, addressing cost governance that becomes critical as AI code review scales across large teams.
Evidence excerpt
Organization owners can now choose to bill the organization that owns the repository instead.