Copilot Code Review Adds Adaptive: Test Depth, Secrets, and Context on Two PR Types
Use a small fix and a cross-repository change to test review effort without replacing protection rules or human approval
GitHub announced Adaptive effort for Copilot code review on November 17, 2026, together with public previews for cross-repository public context and secret detection. Balanced remains the default, and administrators can cap the maximum effort level. This guide validates the change with two pull-request types: a small fix for speed, false positives, and missed issues, and a cross-repository change for context references, secret warnings, and actionable suggestions. Keep branch protection, required human review, tests, and dedicated secret scanning in place. Expand automatic review only when comments can be verified against code and tests without slowing the critical path. This article did not enable the preview or review a production repository.
Key takeaways
By ENHE AI · 2026-11-20 · AI-assisted drafting; pre-publication quality checks completed.
Choose two PR types
Use a small fix with known answers and record time to first comment, valid findings, false positives, and misses. This shows whether Adaptive over-processes simple work.
Use a change that needs public cross-repository context, prelisting the interface that should be referenced and private content that must not appear. Results need traceable files or documentation.
Administrators control effort
Balanced remains the default and administrators can cap effort. Compare Adaptive with Balanced in a non-critical repository before treating Max as a default target.
For each effort change, log repository, PR type, start, and finish. If review slows merging without adding verifiable findings, return to a lower level.
Treat secret warnings as incident signals
Preview secret detection can supplement review, but it does not replace Secret Scanning, pre-commit checks, or secret management. Never copy a full suspected secret into a comment.
If a credential is real, stop the merge, revoke or rotate through the existing process, and inspect history and logs. This article performed no rotation.
Keep required controls
Developers must verify Copilot comments against code and tests. Branch protection, CODEOWNERS, required approvals, and CI remain merge conditions.
Completion requires itemized results for both PR types, no unauthorized context, correct secret handling, and unchanged merge rules. Otherwise mark the pilot partial.
FAQ
Does Adaptive always choose the best effort?
It adjusts effort, but administrators can cap it and representative PRs still need validation.
Does a clean secret review prove the repository has no secrets?
No. It is a preview signal and does not replace dedicated scanning or human response.
Fact evidence
- Adaptive review effort is available in public preview alongside Lite, Balanced, and Max. — GitHub Changelog — Copilot code review adaptive effort, secret detection, and more
- Balanced remains the default, and administrators can cap the maximum effort level. — GitHub Changelog — Copilot code review adaptive effort, secret detection, and more
- Cross-repository context can include public repositories. — GitHub Changelog — Copilot code review adaptive effort, secret detection, and more
- Secret detection in Copilot code review is also in public preview. — GitHub Changelog — Copilot code review adaptive effort, secret detection, and more
Related tools and reading
These production pages support the same decision, workflow, or safety boundary.
Conclusion
Adaptive is useful only if it changes effort across simple and complex PRs without weakening established controls. Gather reviewable data from both types before changing defaults.
What this means for everyday users
Developers must verify Copilot comments against code and tests. Branch protection, CODEOWNERS, required approvals, and CI remain merge conditions.
Related reading
GitHub Launches a Purpose-Built AI Model for Leaked Secret Detection
GitHub announced a purpose-built leaked-secret detection model on October 7, 2026. The model uses surrounding code to identify likely credentials, including passwords that do not follow a recognizable token format. Existing AI-detected alerts remain included with GitHub Secret Protection and GitHub Advanced Security, while the newer push-protection checks and Copilot security-review checks require explicit opt-in and are planned to consume AI Credits. This article separates the three surfaces so teams do not confuse an included repository scan with a credit-consuming pre-push or agent review. It also gives a practical response sequence: verify the finding, revoke and rotate an exposed credential, remove it from active code and history where appropriate, review access logs, set a budget with a real stop rule, and preserve evidence for follow-up.
GitHub Copilot Code Review Adds Max and Approvals: Which PRs Merit Extra AI Credits?
GitHub announced the Max effort level for Copilot code review in public preview and made Copilot approvals generally available on October 28, 2026. Max runs several independent review agents across models from different providers, then uses an aggregation agent to reconcile findings and check accuracy. It is designed for higher-risk changes, but it takes longer and consumes more AI credits than Lite or Balanced. Copilot approvals are off by default and can count toward a repository's required approvals when enabled. A new commit dismisses an earlier approval. This article provides a practical decision rule based on change risk, credit cost, and approved file paths before a team expands the feature.
GitHub Code Scanning Adds AI Application Risks: Check Prompt Injection, Disclosure, and Excessive Agency
GitHub has introduced a public preview of code scanning for AI applications and agent vulnerabilities. The detector covers risks such as indirect prompt injection, sensitive information disclosure, and excessive agency, and runs on pull requests alongside existing CodeQL analysis when the required scans are enabled. It flags code paths where untrusted content can reach a model that has access to tools, data, or business systems. This article turns the announcement into a focused verification workflow: confirm prerequisites, create harmless test cases, review alerts in context, reduce permissions, rerun scans, and preserve human approval. The preview requires GitHub Advanced Security and is not currently available on GitHub Enterprise Server.
GitHub Copilot Browser Use Enters Preview: Test Signed-In Sessions and Permissions Read-Only First
GitHub released Browser Use in public preview on November 17, 2026 for Copilot CLI, the Copilot app, VS Code, and JetBrains, paired with the GitHub Copilot Chrome extension. This guide starts with a read-only acceptance path. Use a test account and a fixed page, confirm that the extension reports Connected, record the tab scope and site permissions, and compare the elements and screenshots the agent uses with the expected page. Then verify that sign-in, form submission, deletion, and external communication stop for explicit approval. Expand only after the read-only flow is repeatable, permissions can be revoked, and failures do not cause unintended actions. The article does not claim a hands-on browser-use test or permission behavior beyond GitHub's documentation.
Gemini 4 Neon Reaches GitHub Copilot: Compare Cost per Accepted Result, Not List Price Alone
GitHub announced Gemini 4 Neon as generally available in Copilot on November 18, 2026 for Pro+, Max, Business, and Enterprise users. It uses provider list pricing under usage-based billing, administrators can manage access through model policy, and availability is rolling out gradually. This article proposes a same-task comparison instead of a list-price decision. Freeze three representative tasks and their inputs, then record accepted results, human edits, tool calls, elapsed time, and billed cost for Neon and the current model. If the model is missing, check plan, client, rollout, and policy before assuming an outage. Change the default route only when both outcome quality and total task cost meet the baseline. No model run, benchmark, or bill was performed for this article.
GitHub Copilot Evals Enters Preview: Regression-Test Skills, Agents, and MCP Changes
GitHub launched Copilot Evals in public preview on November 17, 2026. It creates repeatable tests for skills, custom agents, and MCP tools and lets users compare runs before and after a customization change. This guide defines a minimum regression set: choose three realistic tasks, then specify the input, allowed tools, success criteria, and prohibited behavior for each. Preserve at least one baseline run and one post-change run, including the result, execution path, failed checks, and human review. Merge a customization only when the change preserves the original task, permission boundary, and evidence chain. A single passing answer is not enough because model output can vary, and an automated check cannot decide every domain-specific quality or safety question.
