Copilot code review: New organization billing options and controls
By Steven Van ·
Organization billing requires paid AI Credits usage, and repository admins cannot override an organization’s review request restriction.
Organization owners can now charge licensed members’ Copilot code reviews to the organization that owns the repository, preserving members’ quotas. GitHub also added controls for review requests made with licenses from outside the organization or enterprise.
Choose who pays for reviews
The “Choose how members with a Copilot license are billed” setting is available in organization settings under Copilot, then Policies. It has two options:
- Member, the default, charges the member’s own Copilot entitlement. If their quota is exhausted, the review fails.
- Organization charges the organization that owns the repository. AI Credits paid usage must be enabled, and owners can optionally set a budget.
For Copilot Business and Copilot Enterprise, reviews stop when the applicable budget or spending limit for the selected billing source is exhausted.
Restrict requests from external licenses
Organization owners and repository administrators can enable “Only allow Copilot code review to be triggered by authorized users” for an organization or a single repository. This restricts requests from people using personal licenses or licenses supplied by another organization. Repository administrators cannot disable a restriction enabled at the organization level.
With the setting enabled, Copilot is not offered as a reviewer to unauthorized people, and their API requests do not start reviews. Automatic reviews from their personal settings also do not run, but reviews configured through repository or organization rulesets still run. In personal repositories, only the owner or a direct collaborator can request a review.
The Copilot code review documentation explains how external-license restrictions apply.
