GitHub code scanning's AI Scan for repositories can now be switched on or off at org and repo level through the REST API (public preview)
AI code scanning can now be rolled out in bulk from scripts and infrastructure as code. The endpoints, inheritance rules and billing.
// Key points
- A repository_scan setting is added to the existing AI Scan enablement endpoints: GET / PATCH /orgs/{org}/code-scanning/ai-scan and /repos/{owner}/{repo}/code-scanning/ai-scan.
- If an org disables it, repos cannot enable it; if the org enables it, repos inherit and can opt out; an enterprise policy that blocks it returns 422; updating it with pr_scan in one request is all-or-nothing.
- Enabling it does not start a scan; users with write access run scans on demand, and each scan consumes GitHub Code Security AI credits.
- It covers org-owned public repos and private or internal repos with GitHub Code Security or Advanced Security; GitHub Enterprise Server is not supported.
Builder's takeAs more code is written by AI, AI scanning should be managed as configuration like CI, not clicked on repo by repo. I would enable it at org level and let people with write access run it on demand; since every scan costs credits, try it on core repos for a month and count how many findings are real.
// Background · from #Coding agents
Full timeline →- Nov 15 Gemini 4 Hydrogen is generally available in GitHub Copilot: billed at provider list price across IDEs, the CLI, the coding agent and the Copilot SDK
- Nov 15 The GitHub Copilot app supports GitHub Enterprise Server, moving from preview to general availability
- Nov 14 GitHub Copilot retires six models on December 14, including Claude Fable 5, Gemini 4 Argon and Grok 4.6, each with a suggested replacement