Original announcement: GitHub · 2026-11-07. Read the official announcement.
Summary of the Update
On November 7, 2026, GitHub announced enhancements to its Copilot code review feature. The update enables the management of Copilot code review settings via REST and GraphQL APIs across enterprise, organization, and repository levels. It also introduces a more compact review overview comment format and fixes related to billing, automatic reviews, and reliability. These improvements are available to GitHub Copilot Pro, Pro+, Max, Business, and Enterprise plan users.
What Changed: API Management and Review Identification
- Developers and administrators can now identify Copilot-generated reviews and comments explicitly in API responses, including metadata like review effort, skills, MCP servers, and custom instructions used as sources.
- Enterprise administrators can enable or disable code reviews globally or delegate this decision to organization admins.
- Organization administrators gain control over code review enablement, default review effort, and runner configurations, with enterprise policies taking precedence.
- Repository administrators can adjust review effort settings and toggle usage of custom instructions and MCP tools for reviews.
- The REST API supports the same review effort levels as the GitHub web interface, improving consistency.
- There are constraints regarding token permissions: enterprise and organization settings endpoints do not support GitHub Apps or fine-grained personal access tokens, whereas repository settings support both with appropriate permissions.
Improved Review Overview Comment
- The review overview comment is now more compact, consolidating findings at the top and moving review effort and surveys to a footer.
- Files that are skipped or excluded share a combined “Files not reviewed” section featuring filenames and linked exclusion reasons.
- Empty sections are omitted, and long file lists show an overflow count to reduce clutter.
- Users can provide feedback on the review overview directly by expressing disapproval and specifying the problem, helping GitHub improve Copilot’s review quality.
Additional Enhancements and Reliability Fixes
- Sessions with Copilot code review now display AI credit consumption for greater transparency.
- Automatic review requests respect configured bypass lists for exempt actors to avoid unwanted reviews.
- Improved wording and UI layout for code review organization and repository settings pages to enhance usability.
- Subsequent reviews hide findings unrelated to recent changes for a focused experience.
- Balanced effort reviews employ multiple reviewer models, combining their findings for thorough assessments.
- Bug fixes address billing preservation when toggling code review, automatic retries for failed or timed-out reviews, handling of bot-authored pull requests with appropriate licensing, and preventing false failure reports.
- Ongoing reviews during service updates receive additional time to complete, and feedback surveys respect organizational opt-outs.
Who Should Care?
This update benefits various stakeholders within development organizations using GitHub Copilot code review:
- Enterprise and organization administrators can now centrally control and customize review settings via APIs.
- Repository administrators can fine-tune review parameters at repository granularity.
- Developers receive clearer and more concise review overviews, making feedback easier to parse.
- Integrators and tool authors leveraging Copilot’s API can automate and manage review workflows more effectively.
Next Steps for Developers and Admins
If you use GitHub Copilot code review, especially in managed enterprise or organization environments, consider the following:
- Verify your current review settings and determine if API-based management can improve your workflow.
- Review token permissions and roles to ensure proper access for managing review configurations.
- Familiarize yourself with the new compact review overview format and encourage your team to provide feedback to improve Copilot’s suggestions.
- Check automatic review rules and bypass lists to ensure expected behavior for bots or specific actors.
- Monitor billing and review reliability improvements to confirm that your usage aligns with expectations.
For detailed API configuration guidance, refer to GitHub’s official documentation on configuring Copilot code review with the API.
Checklist
- Confirm administrative roles and their permissions for API management.
- Test REST or GraphQL API calls to read and update code review settings.
- Review existing repositories’ automatic review settings and update bypass lists if necessary.
- Explore the new review overview comments and gather team feedback.
- Monitor any billing or review reliability issues to leverage fixed bugs.
