--- title: Organization-level targeting for GitHub Code Quality description: GitHub now allows organization owners to target specific subsets of repositories when enabling or disabling GitHub Code Quality, instead of applying the... canonical: https://daily.dev/posts/organization-level-targeting-for-github-code-quality-eivvvumus twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Organization-level targeting for GitHub Code Quality | daily.dev og:description: GitHub now allows organization owners to target specific subsets of repositories when enabling or disabling GitHub Code Quality, instead of applying the... og:url: https://daily.dev/posts/organization-level-targeting-for-github-code-quality-eivvvumus og:image: https://api.daily.dev/og/posts/EiVvvuMUs.png og:image:alt: Organization-level targeting for GitHub Code Quality og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Organization-level targeting for GitHub Code Quality **[GitHub Changelog](https://daily.dev/sources/github_updates)** · 1 min read · 0 upvotes · 0 comments ## Summary GitHub now allows organization owners to target specific subsets of repositories when enabling or disabling GitHub Code Quality, instead of applying the setting to all repositories at once. Selection can be done via custom properties, manual selection, repository visibility, or fork status. Admins can also enforce the setting to prevent repository administrators from overriding it. The feature is in public preview for GitHub Enterprise Cloud and GitHub Team plans. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Can I enable GitHub Code Quality for only some repositories in my organization instead of all of them? Yes, organization owners can now target a subset of repositories rather than applying Code Quality to the entire organization at once. Repositories can be selected by custom properties, manual selection, repository visibility, or fork status, and the setting can be enforced so repository administrators cannot override it. This feature is in public preview for GitHub Enterprise Cloud and GitHub Team plans; it is not available on GitHub Enterprise Server. _Teams rolling out code quality checks selectively can follow updates like this on daily.dev._ ## Similar posts on daily.dev - [Organization-level enablement for GitHub Code Quality](https://daily.dev/posts/organization-level-enablement-for-github-code-quality-kf8jc8ojw) · GitHub Changelog · 0 upvotes · 0 comments - [GitHub Code Quality: Organization-level dashboard in public preview](https://daily.dev/posts/github-code-quality-organization-level-dashboard-in-public-preview-gkajqikca) · GitHub Changelog · 0 upvotes · 0 comments - [Organization custom properties now generally available](https://daily.dev/posts/organization-custom-properties-now-generally-available-wlfiy4dov) · GitHub Changelog · 1 upvotes · 0 comments - [GitHub Code Quality enterprise policy](https://daily.dev/posts/github-code-quality-enterprise-policy-lwyraqlud) · GitHub Changelog · 0 upvotes · 0 comments --- Tags: [#devops](https://daily.dev/tags/devops), [#github](https://daily.dev/tags/github) [View this post on daily.dev](https://daily.dev/posts/organization-level-targeting-for-github-code-quality-eivvvumus) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Organization-level targeting for GitHub Code Quality","url":"https://daily.dev/posts/organization-level-targeting-for-github-code-quality-eivvvumus","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/organization-level-targeting-for-github-code-quality-eivvvumus"},"datePublished":"2026-07-09T16:15:58.368Z","dateModified":"2026-09-14T08:01:14.951Z","description":"GitHub now allows organization owners to target specific subsets of repositories when enabling or disabling GitHub Code Quality, instead of applying the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/040aa9db3519d0a11a625a04644e1d00?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/040aa9db3519d0a11a625a04644e1d00?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/organization-level-targeting-for-github-code-quality-eivvvumus","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devops,github","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Organization-level targeting for GitHub Code Quality"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/organization-level-targeting-for-github-code-quality-eivvvumus#faq","mainEntity":[{"@type":"Question","name":"Can I enable GitHub Code Quality for only some repositories in my organization instead of all of them?","acceptedAnswer":{"@type":"Answer","text":"Yes, organization owners can now target a subset of repositories rather than applying Code Quality to the entire organization at once. Repositories can be selected by custom properties, manual selection, repository visibility, or fork status, and the setting can be enforced so repository administrators cannot override it. This feature is in public preview for GitHub Enterprise Cloud and GitHub Team plans; it is not available on GitHub Enterprise Server. Teams rolling out code quality checks selectively can follow updates like this on daily.dev."}}]} ```