GitHub Code Quality became generally available on July 20, 2026 for GitHub Team and GitHub Enterprise Cloud. The product combines deterministic CodeQL analysis with AI-assisted detection for maintainability and reliability issues, while Copilot Autofix proposes changes for review.

What changed at general availability

The GA release adds organization-wide enablement and dashboards, code coverage metrics from existing Cobertura XML reports directly on pull requests, and quality gates through GitHub rulesets. Teams can enforce coverage thresholds, begin in evaluate mode before blocking merges, and use APIs to manage enablement or retrieve findings.

GitHub says its own engineering teams resolve 67.3% of Code Quality findings before merge. That is GitHub’s internal result, not a guarantee for other organizations, so teams should measure precision, remediation rate and developer acceptance in their own repositories.

Why this matters for QA engineers

This release puts several quality signals in the pull-request path where QA and engineering already make release decisions. Coverage deltas, maintainability findings and AI-proposed fixes can become reviewable evidence instead of separate reports discovered late in the cycle.

  • Start in evaluate mode and record which findings would have blocked a merge.
  • Validate every Copilot Autofix with unit, integration and regression tests before accepting it.
  • Set coverage gates around risk and changed code, not a single vanity percentage.
  • Track false positives, accepted fixes, escaped defects and scan cost during a pilot.

Availability and cost to review

GitHub Code Quality is a standalone paid product and is not available on GitHub Enterprise Server at launch. GitHub lists a base charge of $10 per active committer per month, metered usage for AI-assisted detection and Copilot Autofix, and compute costs for deterministic CodeQL analysis in GitHub Actions. A Copilot subscription is not required for the AI-powered features.

Organizations that used the public preview were moved into the paid GA service without migration steps, so administrators should review enabled repositories and budgets now that billing has started.

Sources