GitHub Code Quality is GA, and billing now starts automatically

GitHub Code Quality left preview on July 20, 2026, and the practical change is billing. The product is now generally available on GitHub Team and GitHub Enterprise Cloud, with charges starting automatically for organizations that kept it enabled during the preview.

That makes this more than another Copilot-adjacent changelog entry. Teams now need to check where Code Quality is enabled, who counts as an active committer, and how AI-powered findings, Copilot Autofix, and CodeQL scans can add cost on top of the base license.

GitHub Code Quality now ships as a paid Team and Enterprise Cloud product

GitHub says Code Quality combines deterministic CodeQL analysis with AI-assisted detection to flag maintainability and reliability issues inside pull requests. Copilot Autofix can suggest fixes before merge, while organization dashboards, quality gates, coverage metrics, and APIs give platform teams a central way to manage rollout.

The GA scope matters. GitHub lists availability for GitHub Team and GitHub Enterprise Cloud, not GitHub Enterprise Server at launch. That distinction keeps self-hosted Enterprise Server customers out of this billing event, while cloud organizations that tested broadly during preview may already have repositories covered.

GitHub also disclosed an internal adoption signal: its engineering teams resolve 67.3% of Code Quality findings before merging pull requests. Treat that as a product-side metric, not a guarantee for every repository. The value depends on language coverage, existing CodeQL setup, test reports, review culture, and whether teams actually review Autofix suggestions instead of merging them blindly.

The July 20 switch turns preview usage into billable usage

The base price is $10 per active committer per month. GitHub defines an active committer as someone who pushed a commit to a repository where Code Quality is enabled within the last 90 days. A person is counted once across the organization, and bot accounts are excluded.

That base license is only one part of the bill. GitHub says AI-powered work, including AI-assisted detection and Copilot Autofix, uses usage-based billing. Deterministic CodeQL analysis also consumes GitHub Actions compute, whether the organization uses GitHub-hosted or self-hosted runners.

For preview users, the immediate question is not whether Code Quality works. It is whether the scope still matches the budget. A broad preview across monorepos, platform repositories, or archived-but-still-active projects can pull more committers into the 90-day count than the current team expects.

What admins should audit this week

Start with enablement. Confirm which organizations and repositories have Code Quality turned on, then compare that list against the teams that still need it. Repositories used for trials, migrations, or shared internal frameworks deserve extra attention because their committer history may be wider than their current ownership.

Next, check cost centers and billing visibility. The base license is predictable once the active-committer count is known, but AI usage and Actions compute can vary with pull request volume and ruleset enforcement. If Code Quality findings are allowed to run everywhere, the usage profile can look different from a small preview.

Finally, decide how strict the gates should be. GitHub added ruleset-based quality gates, including coverage thresholds and an evaluate mode. Evaluate mode is the safer rollout path for teams that want signal before blocking merges, especially if Code Quality is new to a repository or if test reports are inconsistent.

This is a platform governance change, not just a reviewer feature

GitHub is positioning Code Quality as part of the AI-era review stack: more generated code, more automated suggestions, and more need for repeatable gates. That is useful, but it shifts responsibility to admins. Once billing is live, leaving preview settings untouched is a spending decision.

Teams already using GitHub Advanced Security should also note the packaging line. GitHub says Code Quality is complementary to GitHub Advanced Security, not bundled with it. Existing security budgets may not automatically cover this new code-health layer.

For teams building AI-assisted development workflows, pair this with LinkLoot's broader AI agent tools guide: agentic coding gets safer when review, cost control, and merge policy are treated as the same operating system.

Evidence

GitHub's July 20 changelog is the primary source for the GA date, pricing model, available plans, new capabilities, and automatic billing start. GitHub's documentation provides implementation context for Code Quality itself. Independent coverage framed the same July 20 billing switch as an audit deadline for organizations that enabled the preview widely.