SNACK: 3-line summary
- GitHub added organization billing and review-request controls for Copilot code review on October 8.
- Teams can preserve members’ quotas by billing the repository-owning organization, which must enable paid AI Credits usage.
- A separate setting can limit review requests to people with licenses supplied by the organization or enterprise.
GitHub’s October 8 update lets organization owners charge Copilot code reviews to the organization that owns the repository instead of consuming licensed members’ own quotas. Administrators also get a separate control over which licenses people can use to request a review.
Snackgirls react
AIKO: I like that the billing switch doesn’t double as an access badge. The accounts ledger has enough responsibilities without becoming the permission list.
Red: I’d save my quota for working through a tricky gameplay idea. Before handing reviews to the team budget, though, I’d want to know how much room it has.
Organization billing is a choice, not the new default
The default remains Member: code reviews associated with organization members who have a paid Copilot license use that member’s own Copilot entitlement. If the member’s quota is exhausted, the review fails.
Organization owners can switch to Organization under Copilot → Policies, using the setting Choose how members with a Copilot license are billed. The organization must enable paid usage for AI Credits; setting a budget is optional.
The choice covers both manually requested and automatic code reviews. It changes billing only and does not grant access to code review. If an applicable organization budget, cost-center budget or enterprise spending limit is exhausted, reviews are blocked alongside other features that consume AI Credits.
A personal license does not have to be enough
By default, people with a paid Copilot license can request reviews in repositories they can access. Organization owners and repository administrators can enable Only allow Copilot code review to be triggered by authorized users to require a license supplied by the repository-owning organization or enterprise.
Here, external describes the license, not the person: a personal license or one supplied by another organization counts as external. A member of the team using such a license can therefore be affected by the restriction.
If the setting is enabled at the organization level, repository administrators cannot turn it off.
Ruleset-based automatic reviews still run
With the restriction enabled, unauthorized people are no longer offered Copilot as a reviewer, and their API review requests do not start a review. Automatic reviews from their personal settings also do not run.
Automatic reviews configured through repository or organization rulesets still run. When configuring the update, teams should make two separate decisions: which account covers review usage, and which licenses allow someone to request a review.
Sources and date: 2026-10-10
Comments
0No login needed. Edit or delete your comment from the same browser.
All comments 0
한국어 · English · 日本語No comments yet. Start the conversation.