Check GitHub Code Quality costs before July 20 billing starts

GitHub has added a Code Quality license estimate so organizations can see expected per-committer costs before billing begins. Confidence level: confirmed. The practical deadline is July 20, 2026, when GitHub Code Quality leaves public preview and starts incurring charges for enabled organizations.

What changed

GitHub announced on July 13, 2026 that enterprise and billing admins can now see active committer usage for repositories using GitHub Code Quality. The estimate appears on the billing entity's Billing and licensing page under Licensing, where the Code Quality card shows consumed licenses and an estimated monthly payment.

The estimate is useful because Code Quality becomes a paid product on July 20, 2026. GitHub says the preview estimate reflects standard list pricing and the active committers that would be billed, but it does not include every cost surface.

Key takeaways

• GitHub Code Quality is still free during preview, except for Actions minutes already consumed by scans.
• Billing starts on July 20, 2026 for organizations that leave Code Quality enabled.
• The new license estimate covers per-committer cost, not Actions minutes or AI-credit usage.
• GitHub Team and GitHub Enterprise Cloud are covered; GitHub Enterprise Server is not.
• Admins should use the estimate as a decision tool, not as a full invoice forecast.

Availability and access

The estimate is available in the Billing and licensing area for the relevant billing entity. GitHub says Code Quality is available on GitHub Team and GitHub Enterprise Cloud.

During the public preview, scans of private repositories do not bill for AI credits or active committer usage, but GitHub Actions minutes are consumed. After general availability, GitHub's billing docs list three cost types: Actions minutes, GitHub AI Credits, and active committer licenses.

Practical LinkLoot angle

This is a platform-budget check, not a code-quality hype cycle. If Code Quality was enabled broadly during the preview, treat the next few days as a cleanup window. Identify repos where merge-blocking quality gates, coverage checks, or AI findings are worth paying for, then disable the rest before billing starts.

For agent-heavy teams, the AI-credit line matters. More generated code usually means more pull requests, more review findings, and more automated fixes. A tool that looked free during preview can become a recurring governance cost once agents increase code volume.

For adjacent automation planning, keep LinkLoot's workflow hub nearby: /guides/ai-workflow-automation.

What to verify before you act

• Open Billing and licensing, then check the Code Quality consumed-license estimate.
• Export or review Actions usage for dynamic/github-code-scanning/codeql.
• List repositories and organizations where Code Quality is enabled but not required.
• Check whether AI findings, Copilot Autofix, or Copilot code review are part of your expected usage.
• Confirm account discounts or contract terms before using list pricing in budget forecasts.

Source check

Confirmed by:

• GitHub's July 13 changelog confirms the license estimate, where to find it, July 20 billing date, $10 per active committer list price, and the limits of the estimate.
• GitHub's billing docs confirm that Code Quality GA starts July 20, 2026 and describe Actions minutes, AI credits, and active committer licenses as the post-GA cost surfaces.

Independent context:

• DevOps.com independently covered the GA billing shift and framed the decision for teams that adopted Code Quality during preview. Treat its adoption and market commentary as context; use GitHub's own docs for billing decisions.