GitHub Copilot code review service exposes an API and changes the default effort level to Balanced
Code review in the GitHub Copilot code review service can now be requested via the REST API and GraphQL API with a custom effort level for each request. Starting 28 September 2026, the default option uses the Balanced level; an explicitly set Lite level remains unchanged.
GitHub has made it possible to request a code review in the GitHub Copilot code review service via the REST API and GraphQL API. Each request can optionally specify a custom effort level. The changes are generally available for the Pro, Pro+, Max, Business, and Enterprise plans. According to GitHub, code review can be integrated this way into custom scripts, workflows, and internal tools.
Starting 28 September 2026, the Default option uses the Balanced level for both new and existing repositories and organizations using the GitHub Copilot code review service. An explicitly chosen Lite level has been preserved. Users can change the Default option to Lite in the settings they manage; a setting at a lower level can override the setting at a higher level.
Why it matters
Developers can specify the effort level for individual reviews and verify how the change to the default option will affect their settings. Teams can run code reviews from their own systems via the API and incorporate it into their existing change review process.
Two audiences, two different impacts
What this means
For individuals
If you use the Default option, your reviews will use the Balanced level starting 28 September 2026. An explicitly set Lite level has not changed.
For a business
Teams can incorporate code review runs into internal tools and workflows via the REST API or GraphQL API, and specify the effort level for each request.
DevelopmentCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.