GitHub Code Quality becomes a paid product on July 20
GitHub Code Quality leaves public preview on July 20, 2026 with per-committer pricing, AI usage charges, and organization-wide quality controls.
GitHub Code Quality becomes generally available as a paid product on July 20, 2026. The announcement says the service will cost $10 per active committer per month on enabled repositories, with separate usage charges for AI-powered capabilities and GitHub Actions minutes for deterministic CodeQL analysis. GitHub Docs confirms Code Quality is currently in public preview, is available for organization-owned repositories on Team and Enterprise Cloud, and is not available on GitHub Enterprise Server.
Key takeaways
- The public preview ends on July 20, 2026, when Code Quality becomes a purchasable GitHub product.
- The base price is $10 per active committer per month on enabled repositories.
- AI-powered features such as Copilot code review, AI-assisted detection, and Copilot Autofix add metered usage.
- Deterministic CodeQL maintainability and reliability scans consume GitHub Actions minutes.
- Teams that do not want the paid version should disable Code Quality on enabled repositories before July 20.
Practical LinkLoot angle
This is a budgeting and governance story, not just a feature launch. Engineering leads should map enabled repositories, active committers, Actions usage, and Copilot review volume before July 20 so Code Quality does not turn into a surprise line item.
| Decision area | What changes | Check before rollout | Source |
|---|---|---|---|
| Licensing | Per-active-committer billing starts at GA | Count committers on enabled repositories, not just total org seats | GitHub Changelog |
| AI usage | Copilot review, AI detection, and Autofix are metered | Separate mandatory quality checks from optional AI assistance | GitHub Changelog |
| Deterministic scans | CodeQL analysis uses Actions minutes | Review runner capacity and Actions budgets | GitHub Changelog |
| Availability | Team and Enterprise Cloud org repos are in scope | Confirm plan, repository ownership, and Enterprise Server exclusions | GitHub Docs |
The useful workflow is simple: keep Code Quality enabled on a pilot set, export the repository list, estimate active committers, then decide which checks should block merges through rulesets. For larger organizations, the new organization-wide deployment and quality dashboards are the main reason to test it before the billing date.
What to verify before you act
Check which repositories have Code Quality enabled today and whether any of them are high-churn projects with many active committers. Confirm whether your quality gate depends on AI-powered features, because those charges are separate from the $10 base subscription. Also verify Actions minute budgets, since deterministic CodeQL analysis is billed through Actions consumption rather than AI Credits.
GitHub says Code Quality becomes generally available on July 20, 2026.
For adjacent AI development tooling, see LinkLoot's guide to AI agent tools.