Original announcement: GitHub · 2026-11-17. Read the official announcement.
Summary of GitHub Copilot Code Review Updates
On November 17, 2026, GitHub introduced new features to its Copilot code review tool aimed at enhancing review efficiency and security. These features—currently in public preview—include adaptive review effort selection, cross-repository context awareness, and secret detection during pull request reviews.
What Has Changed?
- Adaptive Review Effort: Copilot automatically determines the appropriate level of review effort (Lite, Balanced, or Max) based on the complexity and risk of each pull request.
- Cross-Repository Context: Copilot can now reference related public repositories during reviews, providing broader context about how changes might affect dependent code and documentation elsewhere.
- Secret Detection: Copilot scans pull requests for exposed secrets (such as credentials) using both deterministic methods supported by a partnership of over 150 technical collaborators and AI/ML models, alerting developers before code merges.
- Azure DevOps Integration: Copilot code review for Azure Repos has exited public preview and is generally available with flexible setup options, customized feedback, and tracking features.
Who Should Care?
These enhancements are important for developers, code reviewers, and teams who rely on GitHub Copilot to maintain code quality and security, especially those working across multiple repositories or using Azure DevOps. Teams on Copilot Pro, Pro+, Max, Business, or Enterprise plans gain access to these features, facilitating better tailored and more secure code reviews.
Next Steps for Developers
- Enable Adaptive Review Effort: Developers or organizations can configure Adaptive mode as the default or select it per pull request in settings to automate review depth based on risk.
- Leverage Cross-Repository Context: Understand that Copilot can pull insights from related public repositories during reviews, making multi-repo impact assessments easier.
- Activate Secret Detection: Turn on secret detection in repository or organization settings under Copilot code review to get alerts on exposed credentials within pull requests.
- Review Outcomes Tracking: Use the Insights tab in repositories to monitor how Copilot feedback is addressed, improving code review governance.
- For Azure DevOps Users: Configure Copilot code review integration, adjust review effort levels, and customize instructions to optimize team workflows.
Practical Checklist
- Confirm your GitHub plan supports these new features (Pro, Pro+, Max, Business, or Enterprise).
- In repository or organization settings, enable Adaptive review effort for automated review depth.
- Enable Secret detection to catch exposed secrets before merging.
- For public repositories, be aware cross-repository context is active in public preview and can enhance review quality.
- Use repository Insights to track Copilot review feedback and outcomes.
- Azure DevOps teams should activate Copilot code review from organizational settings and customize as needed.
Conclusion
GitHub’s enhancements to Copilot code review aim to reduce manual configuration, improve detection of potential issues, and incorporate broader context during code reviews. As these features reach public preview and general availability stages, developers and teams should evaluate their integration and configuration to gain better code quality and security outcomes.


