GitHub opens Copilot code review to API workflows
GitHub adds REST and GraphQL review requests with effort controls while plan access, permissions and usage budgets still apply
GitHub made API support for Copilot code review generally available on October 2. Teams can request a review through REST or GraphQL and choose the effort level for that request. The release covers Copilot Pro, Pro+, Max, Business and Enterprise plans.
The practical gain is control over when a review starts. A team could connect the request to an internal development tool or a workflow checkpoint, instead of relying on someone to open the pull request page.
Check permissions before connecting a workflow
The REST endpoint for requesting reviewers requires pull request write permission for tokens with granular repository permissions. It supports GitHub App tokens as well as personal tokens. Its documentation also warns that sending requests too quickly can trigger secondary rate limits.
An organization supplied subscription also requires the organization to enable code review in its Copilot policies. Members without a Copilot license have a separate access option on GitHub.com through Business and Enterprise. That option requires paid usage to be enabled and bills their reviews to the organization or enterprise.
What each review can cost
GitHub’s usage estimates put a Lite review at US $0.05 to $1 in AI credits and a Balanced review at US $0.25 to $5. These are estimates, not fixed prices or spending caps. Larger pull requests and repository instructions can increase consumption. GitHub Actions minutes for the agentic capabilities are a separate cost component and are excluded from those ranges.
Business and Enterprise budget controls still apply. Reviews are blocked when a user budget or the applicable enterprise or cost center spending limit is exhausted.
Balanced changed before the API launch
The default effort change has an earlier timeline. GitHub announced it on August 28, setting September 28 as the date when Default would use Balanced for new and existing repositories and organizations. Explicit Lite selections were preserved.
The October 2 announcement confirms that the switch took effect on September 28. It should not be read as a second new rollout alongside the API support.
GitHub’s configuration guide describes Lite as the standard review and Balanced as deeper analysis of complex changes. The Max subscription in the launch’s plan list should not be confused with Max review effort. The guide still marks that effort option as coming soon and unavailable.
Keep a human decision at the end
GitHub’s responsible use documentation warns that Copilot can miss problems, flag issues that do not exist and suggest inaccurate or insecure code. API access makes review requests easier to automate. Teams still need to inspect the findings and test proposed fixes before accepting them.
A useful first deployment is one repository with a clear review trigger and an owner for the resulting comments. Check the effort used and the actual consumption before expanding the workflow. Faster requests only help if someone can act on the feedback.
Archival photograph Ted & Ian by Lisamarie Babik from April 2007, showing pair programming. Licensed under Creative Commons Attribution 2.0. Resized and converted to WebP.
