Copilot Code Review Adaptive: Power-User Guide to Effort, Secrets and Costs

Last updated: November 21, 2026

GitHub’s November 17, 2026 update to Copilot code review adds Adaptive, a preview setting that picks Lite, Balanced or Max effort for each pull request based on its risk. It also adds secret detection, cross-repository context and review outcome insights, and makes Copilot code review generally available for Azure DevOps.

Contents

What changed on November 17

The GitHub changelog post of November 17, 2026 describes five changes:

  • Adaptive effort (public preview): Copilot reviews each pull request with Lite, Balanced or Max depending on complexity and risk, and shows which level it chose.
  • Cross-repository context (public preview): reviews can read related public repositories to find code that depends on your change.
  • Secret detection (public preview): Copilot flags exposed credentials in review comments before you merge.
  • Repository insights: a new page shows how Copilot review feedback is acted on in each repository.
  • Azure DevOps: Copilot code review for Azure Repos is now generally available.

GitHub states that Adaptive, cross-repository context and secret detection are available to Copilot Pro, Pro+, Max, Business and Enterprise plans.

Review effort levels and costs

Reviews consume AI credits (one credit equals $0.01, per Microsoft) plus GitHub Actions minutes for agentic context gathering. The estimates below come from GitHub’s Copilot code review documentation; GitHub notes that real costs can fall outside these ranges and grow with pull request size and custom instructions.

Setting What it does Typical range per review Average per review
Lite Fast, targeted feedback on bugs, security issues and style $0.05 to $1 $0.25
Balanced (default) Higher-reasoning model for complex logic, security-sensitive code and cross-service changes $0.25 to $5 $1.50
Max (preview) Multiple high-reasoning models for the most scrutiny $1.50 to $25 $10
Adaptive (preview) Copilot picks Lite, Balanced or Max within your configured maximum Depends on the level chosen Depends on the level chosen

How to turn on Adaptive

You can choose Adaptive for one pull request in the Reviewers bar, or make it a default. The steps below follow GitHub’s configuration guide for personal and repository settings.

  1. For your own reviews: click your profile picture, open Copilot settings, then select Code review in the sidebar.
  2. Next to Review effort level, select Adaptive. The choice applies to automatic reviews and to reviews you request manually.
  3. For a repository: open the repository Settings, go to Code, planning, and automation, then Copilot and Code review.
  4. Set Review effort level to Adaptive for automatic reviews in that repository.
  5. Set Maximum review effort to No limit, Lite, Balanced or Max. Adaptive will never pick a level above this cap.
  6. Open a pull request and check the overview comment, which shows the effort level used for each review run.

If no level is chosen anywhere, Copilot falls back to Balanced. A level picked on the request itself always wins over saved defaults.

Secret detection in reviews

Copilot code review now points out exposed credentials in its review comments. According to the changelog, it combines two methods. Known formats are matched deterministically using more than 500 secret types built with over 150 partners in GitHub’s secret scanning partner program. Secrets without a recognizable format are found with LLMs and a purpose-built GitHub model.

To turn it on, go to repository or organization settings, select Copilot, then Code review.

Cross-repository context

With cross-repository context, Copilot can search the default branch of related public repositories during a review on GitHub.com, looking for dependent code, documentation, custom instructions and skills. The documentation says this preview currently covers public repositories. Organization users need the Opt in to preview features policy enabled.

Repository administrators can turn it off with the Search public repositories setting, which is on by default.

Copilot code review for Azure DevOps

Teams on Azure Repos can now get Copilot reviews with line comments and suggested changes. Microsoft’s Azure DevOps documentation describes a three-step enablement: a Project Collection Administrator turns it on under Organization settings > Repos > Repositories, a Project Administrator enables projects, and repository owners enable individual repositories.

  • Effort: projects and repositories can default to Lite or Balanced, and users can pick another level for a single review.
  • Automation: add a branch policy to request a Copilot review automatically on pull requests to a branch.
  • Limits: pull requests must have no merge conflicts, 100 or fewer changed files and 100 or fewer changes, in repositories of 10 GB or less. Concurrency is capped at 5 reviews per organization and 2 per user.
  • Billing: charges go to the linked Azure subscription under the meter subcategory “GitHub Copilot for AzDO” and take about 48 hours to appear.

In Azure DevOps, Copilot leaves only Comment reviews and does not re-review automatically after new commits.

Measuring results with Repository insights

A new Repository insights page, the first item on a repository’s Insights tab, shows four signals, per the repository insights changelog: comments addressed, high-severity comments addressed, pull requests with no later human change request, and merged pull requests without a Copilot review. The same metrics appear in the repos-1-day reports of the Copilot usage metrics API, which require the Copilot usage metrics policy.

Our Copilot code review API and usage metrics guide covers the earlier November API changes.

Workflows and settings that work well

  • Cap cost first. Set the repository maximum to Balanced, watch Repository insights, then allow Max where authentication, payments or release code live.
  • Force Max where it matters. GitHub recommends Max for high-risk or release-critical pull requests and Lite for routine changes.
  • Test instructions in the pull request. Copilot reads .github/copilot-instructions.md, AGENTS.md and skills from the head branch.
  • Watch attribution. Automatic reviews bill the pull request author by default.

For related team controls, see our GitHub Copilot team plugins guide, our GitHub Copilot Evals guide, our Copilot browser use guide and our Copilot app for GHES guide.

Limitations

  • Preview status: Adaptive, Max, cross-repository context and secret detection are public previews and subject to change.
  • No model choice: GitHub says model switching is not supported for code review.
  • Excluded files: dependency files such as package.json, log files and SVG files are not reviewed.
  • Variable cost: GitHub publishes estimates only.

Frequently asked questions

What is Adaptive in Copilot code review?

Adaptive is a review effort setting announced by GitHub on November 17, 2026, in public preview. Instead of you choosing Lite, Balanced or Max, Copilot looks at each pull request’s complexity and risk and picks one of those three levels.

How much does a Copilot code review cost?

GitHub’s documentation estimates an average of about $0.25 per review with Lite, $1.50 with Balanced and $10 with Max, paid in AI credits. GitHub Actions minutes for agentic context gathering are extra.

Which Copilot plans get Adaptive and secret detection?

GitHub says Adaptive, cross-repository context and secret detection are available on Copilot Pro, Pro+, Max, Business and Enterprise plans. All three are in public preview. Copilot Free does not include Copilot code review.

Is Copilot code review available for Azure DevOps?

Yes. Copilot code review for Azure Repos became generally available on November 17, 2026. Administrators enable it at organization, project and repository level, and charges go to the linked Azure subscription through Azure Cost Management.

How do I stop Copilot from reading other repositories?

In the repository settings, under Copilot and then Code review, turn off Search public repositories. The setting is on by default, and cross-repository context currently reads only the default branch of related public repositories.

Sources

Image: GitHub mark (Octicons), by GitHub, MIT license, via Wikimedia Commons. Placed on a white background and resized. GitHub and Copilot are trademarks of GitHub, Inc. FreeAnswers is not affiliated with or endorsed by GitHub.

Related answers

Leave a Comment