GitHub expands AI security checks, but a finding will not block a merge

An AI warning in a pull request does not necessarily stop the change from shipping. GitHub’s October 15, 2026 releases make AI Scan and agentic autofix generally available, but they serve different stages of security work: spotting a possible problem in a proposed change, and preparing a repair for an existing alert.

First, understand what the finding can enforce

AI Scan complements CodeQL in areas such as PHP, Shell, Terraform configuration and Dockerfiles. With the required repository settings enabled, its findings appear beside CodeQL results with an AI label. They are advisory: they do not fail the scanning check or become a merge-blocking ruleset requirement. Fork and Dependabot pull requests are excluded. AI Scan announcement.

For a creator maintaining a small website, that means an extra review signal still needs someone to read it. A suggested fix should explain the risk, preserve the intended behaviour and pass the project’s checks. A green merge button alone does not answer those questions.

Repair works from an eligible default-branch alert

Agentic autofix explores the repository, proposes changes, reruns CodeQL and opens a draft pull request for review. It supports default-branch alerts; an alert found only on another branch cannot be assigned through this workflow. Up to 25 alerts can be grouped for one proposed repair. Autofix release.

Access is narrower than AI Scan: the agentic repair release requires an eligible Code Security or Advanced Security customer on Enterprise Cloud, administrator enablement and a Copilot billing method. The result is a proposal to examine, not a reason to skip your own acceptance checks.

Public availability still has a usage bill

AI Scan is available for public repositories; private and internal organization repositories require the relevant security product. A Copilot licence is not required for AI Scan. Both features use Code Security AI Credits, including on public repositories, and agentic autofix also uses Actions minutes. Review the billed account’s allowance and budget before enabling them broadly. Security billing rules.

Start with one understood alert and inspect the proposed diff and validation. Our AI output evaluation guide and coverage of local Copilot sandboxing explain two useful boundaries around that review.