GitHub Code Quality is now generally available 🚢

[ebndev]

GitHub Code Quality is now generally available on GitHub Enterprise Cloud and GitHub Team.

AI is helping your team ship code faster than ever. Code Quality helps make sure you can trust it. It pairs CodeQL's deterministic analysis with AI-assisted detection to catch maintainability and reliability issues right in your pull requests—and Copilot Autofix suggests a fix you can review before you merge. The feedback shows up where you already work, not in a separate dashboard you have to remember to check.

And it moves the needle: across GitHub's own engineering organization, teams resolve 67.3% of Code Quality findings before merging their pull requests.

Who this is for

Developers and engineering teams who want in-context feedback on the quality of their code, and the leaders who want to see and improve maintainability and reliability across the org without slowing anyone down.

What's new since the public preview

More than 200,000 repositories ran Code Quality during the public preview, and your feedback shaped what shipped for GA:

• Organization-wide enablement and dashboards, so you can see maintainability and reliability scores across all your repositories in one place.
• Code coverage on pull requests, rendered from your existing Cobertura XML coverage reports.
• Quality gates through GitHub rulesets, including coverage thresholds, with an evaluate mode so you can roll out gradually before you start blocking merges.
• APIs to manage repository enablement and fetch findings programmatically.

How it works

• Findings in context: Quality issues surface directly in the pull request, with guidance you can act on right away.
• One-click fixes: Copilot Autofix suggests a fix for you to review before merging.
• Scores you can track: Reliability and maintainability scores summarize findings so you can prioritize and pay down technical debt on your own schedule.
• Deterministic plus AI detection: CodeQL-based rules and AI-assisted detection work together to catch more of what matters.

What it costs

Code Quality is a standalone paid product. It isn't available on GitHub Enterprise Server at launch. You pay a predictable base license plus metered usage:

• $10 per active committer, per month. A committer counts as active when they've pushed to a repository with Code Quality enabled in the last 90 days, and each one is counted only once no matter how many repositories they contribute to. Bot accounts aren't charged.
• Usage-based billing for AI-powered work, including AI-assisted detection and Copilot Autofix. You don't need a GitHub Copilot subscription to use them.
• Compute costs for running CodeQL analysis on GitHub Actions, on both GitHub-hosted and self-hosted runners.

Billing begins automatically at general availability on July 20, 2026. See the GitHub Code Quality billing docs for the full breakdown.

If you used Code Quality in the public preview

There's nothing to migrate or reconfigure. Code Quality keeps running on the agreement you already have, now as a paid product. Since billing is now in effect, review where you have Code Quality enabled. To stop future scans and charges, disable it for a repository or organization.

Go deeper with the learning pathway

Want to get more value from GitHub Code Quality? The Code Quality learning pathway shows how to use quality insights, automation, and governance controls to improve maintainability, reliability, and engineering effectiveness across the SDLC.

Learn more

• About GitHub Code Quality
• Enabling GitHub Code Quality
• GitHub Code Quality billing

We'd love to hear how Code Quality is working for your team. Drop your questions, feedback, and what you'd like to see next in the comments below.

[hfhbd]

Is there any free option to only see test coverage UI without AI with your own tooling that uploads the report, especially for free/open source repositories?

[hfhbd]

Even without GitHub Team subscription? I tried to enable it in my repo using a free org: https://github.com/softwork-app/cikraft, but I got this error message: Code Quality can only be enabled by organizations with an active Code Quality trial or subscription.

[carogalvin]

@hfhbd ah, yes, that is a bug that we are working on - certain types of orgs are blocked from enabling even for public repos where it should be free and available. This is high on our post-release fix list; check back in a few weeks!

[robirtnelson]

same bug for me

[cannist]

The bug causing the Code Quality can only be enabled by organizations with an active Code Quality trial or subscription. message has been fixed.

[smokedlinq]

For legacy repositories, please support coverage thresholds rules on changed code (diff coverage / new code coverage) instead of only aggregate repository coverage. This would allow teams to prevent new coverage debt without requiring immediate remediation of historical debt. Similar to SonarQube's "Coverage on New Code" quality gate.

[carogalvin]

Thanks for this feedback!

[a1exstr]

When are you going to introduce product level budgets for Code Quality?

[carogalvin]

@a1exstr the screenshot did not come through; product-level budget is on our roadmap, in the meantime you should be able to create a SKU-level budget to control the AIC spend for CQ.

[santialbo]

I'm unable to activate it on our private repo. I have enabled it org-wise, but I get the following error when activating it on a specific repo.

[hfhbd]

https://github.com/orgs/community/discussions/201460#discussioncomment-17736578

[cannist]

This should be fixed now. Please try again.

[santialbo]

It works! thanks for the heads up @cannist! We've activated it 😊

[GabrieleBocchi]

Enabling Code Quality organization-wide (Repository access: All repositories) also creates a branch ruleset named "Code Quality Copilot review for default branch" individually on every single repository, with copilot_code_review active (review_on_push: true, review_draft_pull_requests: true).
There's no toggle, not on the organization's "Code quality" settings page, not per-repository, to enable Code Quality without this bundled ruleset.

Is this ruleset creation an intentional, documented part of enabling Code Quality, or a separate policy that happens to run alongside it? Either way, it would be good to have a way to enable Code Quality without the "Automatically request Copilot code review" ruleset getting created on every repository.

[carogalvin]

It was intentional but we have rolled back the auto-creation of the ruleset and will be disabling the ruleset where it was created automatically, based on the feedback we have received. You can expect this rollback to happen AUgust 5
.