GitHub adds organization-level targeting controls for Code Quality preview

GitHub has added organization-level targeting for GitHub Code Quality, giving owners a more selective way to roll the tool out across repositories instead of switching it on or off everywhere at once. The July 9 changelog says organization owners can now choose subsets of repositories from the Code Quality section of organization settings and apply the setting to only those projects.

The change matters for teams that manage many repositories with different risk profiles, maturity levels, or ownership models. Code Quality is GitHub's newer product area for maintainability, reliability, coverage controls, and AI-assisted review workflows. A single organization-wide toggle can be too blunt for large engineering groups, especially when legacy services, active application repositories, internal tools, and forked projects all sit under the same organization.

What changed

GitHub says owners can target repositories using custom properties, manual selection, repository visibility, and fork status. That means a platform team could, for example, require Code Quality on production-facing private repositories while leaving experimental or forked repositories out of scope. The announcement also says owners can enforce the setting on the targeted repositories so repository administrators cannot change it locally.

The release is available as a public preview for GitHub Enterprise Cloud and GitHub Team plans. GitHub also notes that Code Quality is not available on GitHub Enterprise Server, which keeps the feature focused on the hosted GitHub service for now.

Why it matters

Granular targeting is a practical governance feature rather than a flashy developer tool update. It gives central administrators a way to standardize quality checks where they are required without forcing every repository into the same policy. That can reduce rollout friction for organizations that want stronger quality gates but still need staged adoption, exceptions, or different policies for different repository classes.

The timing is also notable because GitHub has been expanding Code Quality ahead of its broader commercial availability. In June, the company said Code Quality would become generally available on July 20, 2026, with a $10 per active committer monthly license on enabled repositories, plus usage-based billing for AI-powered features and GitHub Actions minutes for deterministic CodeQL analysis. More precise repository targeting could help customers manage both policy scope and spend before they commit to a wider deployment.

Sources

• github.blog
• github.blog

Cover photo by Jakub Zerdzicki on Pexels, used under the Pexels License.