GitHub Code Quality, the feature set covering CodeQL analysis, code coverage enforcement, quality gates, and AI-assisted code review, spent its public preview building a large installed base: more than 10,000 enterprises turned it on to catch maintainability and reliability issues before they shipped. On July 20, 2026, it became a paid product, and for organisations that never turned it off after trying it, the bill started the same day.
What actually costs money now
The core charge is straightforward on paper: 10 dollars per active committer per month, applied to every repository where Code Quality is enabled. The complexity is in what sits on top of that flat fee. AI-powered capabilities, Copilot code review, AI-assisted issue detection, and Copilot Autofix, are billed separately on a usage basis, meaning the more your team relies on the AI review layer, the less predictable the monthly total becomes. Deterministic CodeQL analysis, the non-AI static analysis engine, draws down GitHub Actions minutes on every run, which is a cost most engineering teams already track loosely against their existing Actions budget rather than as a discrete line item tied to a specific feature.
The trap is in how GA billing actually turned on
The detail worth flagging to any finance or platform team is that billing began automatically at general availability. Organisations that enabled Code Quality during the free preview to evaluate it, a natural thing to do given the scale of adoption, did not need to take a separate action to start paying for it once GA landed. If nobody on the engineering or procurement side was tracking the preview-to-GA transition date, the first sign of the change is a materially different GitHub invoice arriving weeks later, by which point identifying which repositories, teams, and AI feature usage actually drove the increase takes real reconstruction work.
Why this is worth an actual audit, not a shrug
This is not a reason to turn Code Quality off, the underlying capability, org-wide quality dashboards, coverage enforcement via rulesets, and AI-assisted review, is genuinely useful and was popular enough in preview to justify GitHub charging for it. It is a reason to actually know, per repository and per team, which committers are active on Code Quality-enabled repos, how much of the spend is the flat per-committer fee versus AI usage-based consumption, and whether every repository with it enabled is one your organisation actually wants to pay for going forward. For European engineering organisations already managing tight cloud and tooling budgets against several other 2026 price increases, a silent transition from free preview to per-committer billing is exactly the kind of change that is cheap to catch in the first billing cycle and expensive to unwind six months in.
If your organisation needs help auditing GitHub Actions and Code Quality spend, right-sizing which repositories and teams actually need premium developer tooling enabled, or building ongoing visibility into DevOps tool costs before they show up as a surprise on next month’s invoice, contact Excello Digital. We help European engineering teams keep their tooling spend deliberate rather than accidental.