Browser-local review gate · Source checked September 2, 2026
Is Copilot code review ready for automatic, bot, and large pull requests?
Check assessment versus approval, governance scope, allowed paths, billing, effort, runners, excluded files, human validation, reporting, and fallback without connecting to GitHub or spending AI credits.
Local result
Complete the review evidence
Nine gates remain. Begin with policy scope, approval authority, path limits, billing attribution, runners, and excluded files.
A passing checklist does not certify review completeness, code quality, security, compliance, merge safety, or production readiness.
Continue by rollout decision
Copilot code review readiness questions
No. It runs locally in the browser and does not inspect repositories, read policies, request a review, configure runners, spend AI credits, or collect credentials.
No. GitHub excludes specified file types and locations, and Copilot can miss issues in reviewed files. Assign excluded and consequential changes to other controls and human owners.
No. They consume AI credits and may consume Actions minutes. Resolve the triggering user or designated billing owner, paid-usage policy, budget, and reporting before enabling them.
No. Balanced uses more reasoning and typically more credits, but it cannot guarantee correct or complete findings. Human review and required checks remain necessary.
A bounded pilot must verify policy, assessment versus approval, path scope, required-approval behavior, stale-approval dismissal, billing, effort, runners, exclusions, context permissions, human validation, monitoring, budget denial, and fallback with live evidence.
No. GitHub says every review includes an assessment, but the assessment alone does not count. An actual Copilot approval can count only after the public-preview setting is enabled at the applicable governance levels.
GitHub says the approval is dismissed like a human review. Request a fresh Copilot review if the repository still intends to use a Copilot approval for the updated pull request.
Official references: approval public preview, expanded capabilities, code review concepts and billing, automatic review configuration, and excluded files.