GitHub Copilot

GitHub Copilot code review settings: automatic PR reviews, rulesets, effort level and approvals

How do I make GitHub Copilot review pull requests automatically?

For your own PRs, open Copilot settings, click Code review, and enable Automatic Copilot code review. For a repository or organization, create a branch ruleset with the rule Automatically request Copilot code review. Personal automatic review needs Copilot Pro, Pro+, Max, Business or Enterprise and is not available for managed user accounts.

Review your own pull requests automatically

  • Click your profile picture, then Copilot settings.
  • In the sidebar under Copilot, click Code review.
  • Enable Automatic Copilot code review.
  • Optional: enable Review new pushes.
  • Optional: enable Review draft pull requests.

Your user settings cannot turn off push or draft reviews that a ruleset has enabled. If several sources apply, Copilot still posts one review.

Turn it on for a repository with a ruleset

  • Repository Settings, then Rulesets, then New ruleset, then New branch ruleset.
  • Name it and set Enforcement Status to Active.
  • Under Target branches, add a target such as Include default branch.
  • Under Branch rules, select Automatically request Copilot code review.
  • Optional: Review new pushes (otherwise Copilot reviews once) and Review draft pull requests.
  • Click Create.

For an organization, do the same under organization Settings, Repository, Rulesets, and target repositories by name pattern.

Choose the review effort level

  • Lite: standard review.
  • Balanced: deeper analysis of complex logic, security sensitive code and cross service changes. Uses more AI credits.
  • Max: shown as Coming soon, not available yet.
  • The built in default is Balanced.

Set it per user in Copilot settings, Code review, or per repository in Settings, Copilot, Code review.

Copilot approvals (public preview)

  • Allow Copilot to approve pull requests: lets Copilot submit approving reviews.
  • Allow Copilot approvals to count toward merge requirements.
  • File paths: up to 15 globs, one per line. Approvals count only if every changed file matches.

Limit who can trigger reviews

Enable Only allow Copilot code review to be triggered by authorized users to block reviews requested with an external Copilot license. If an organization enables it, repositories cannot turn it off.

Sources

More on GitHub Copilot

Other guides

Cursor: allow all terminal commandsClaude Code: allow commands without promptsCodex CLI: approval and sandbox modesGemini CLI: YOLO mode, auto_edit and allowing specific shell commandsCursor Privacy Mode: telemetry, training and data retentionClaude Code telemetry and data retention: what is sent and how to turn it offGemini CLI: turn off usage statistics and telemetryCLAUDE.md: where it goes, how it loads, and how it works with AGENTS.mdClaude Code hooks: format on save, block risky edits, get notifiedClaude Code subagents: create one, limit its tools, and call itAdd MCP servers to Cursor with mcp.json: Keep files out of Cursor with .cursorignore: Configure Codex with config.toml: Configure Gemini CLI with settings.json: Add MCP servers to Claude Code (claude mcp add, .mcp.json, scopes): Claude Code custom slash commands and skills (SKILL.md): GitHub Copilot custom instructions: Adding MCP servers to GitHub Copilot: Claude Code settings.json: file locations, precedence, and key settingsClaude Code plugins and marketplaces: install, create, and shareGemini CLI extensions and custom commands: Configuring OpenCode with opencode.json: Cline Rules: workspace, global, and conditional rulesKiro steering files: .kiro/steering, inclusion modes, and AGENTS.mdZed agent: instruction files, MCP servers, tool permissions, and ACP agentsCursor CLI: install, headless mode, permissions and CIAider: CONVENTIONS.md, .aider.conf.yml and API keysJunie guidelines, MCP and the Action Allowlist: Amp AGENTS.md, settings.json and MCP: Configure Goose extensions, hints, recipes and permissions: Customize OpenHands with skills, AGENTS.md, setup.sh and MCP: Configure Factory Droid CLI: AGENTS.md, settings.json, autonomy, custom droids and MCPConfigure Qwen Code: settings.json, providers, QWEN.md, MCP and approval modesCursor hooks: hooks.json, beforeShellExecution, afterFileEdit and exit codesCursor sandbox: sandbox.json, network allowlist and run modesCursor settings: settings.json, Cursor Settings and the ~/.cursor config filesCursor browser agent: @browser, browser automation and approval modesCursor subagents: .cursor/agents, frontmatter, built-in Explore, Bash and BrowserCursor telemetry and OpenTelemetry export (Privacy Mode, OTLP, Analytics API): Cursor rules setup: .cursor/rules, .mdc frontmatter, globs, alwaysApply and AGENTS.mdClaude Code headless mode: claude -p, --output-format json, --bare and CI flagsClaude Code statusline: custom status bar in settings.json with context %, cost and git branchClaude Code /model: switch models, aliasesClaude Code /cost and /usage: check token spend, usage limits and reduce costsClaude Code VS Code extension: install, shortcuts, settings and /ideCodex AGENTS.md: global, project and override instruction files explainedCodex MCP servers: codex mcp add and [mcp_servers] in config.tomlCodex sandbox modes: read-only, workspace-write, danger-full-access and network accesscodex exec: run Codex non-interactively in scripts and CI with JSON outputCodex skills: create SKILL.md, skill folder locations and $skill invocationGEMINI.md in Gemini CLI: context file locations, imports and /memoryGemini CLI MCP servers: gemini mcp add and mcpServers in settings.jsonGemini CLI custom slash commands: TOML files, {{args}}, !{shell} and @{file}Gemini CLI headless mode: gemini -p, JSON output and exit codes for scripts and CIGemini CLI sandbox: enable Docker, Podman, macOS Seatbelt or gVisorcopilot-setup-steps.yml: set up the GitHub Copilot cloudGitHub Copilot CLI permissions: --allow-tool, --deny-tool, --allow-all-tools and trusted directoriesGitHub Copilot custom agents: .github/agents/*.agent.md profiles, tools and frontmatter

Get the weekly agent stack update

New official MCP servers, spec changes and harness releases, checked against the source. One email a week, no fluff.

Reviewed Oct 13, 2026. Settings change often; the linked vendor docs are the source of truth.