{"meta":{"title":"Enabling GitHub Code Quality","intro":"Turn on Code Quality to give your teams a consistent quality baseline: automatically catching, fixing, and reporting code quality issues in pull requests and on your default branch.","product":"Security and code quality","breadcrumbs":[{"href":"/en/code-security","title":"Security and code quality"},{"href":"/en/code-security/how-tos","title":"How-tos"},{"href":"/en/code-security/how-tos/maintain-quality-code","title":"Maintain quality code"},{"href":"/en/code-security/how-tos/maintain-quality-code/enable-code-quality","title":"Enable Code Quality"}],"documentType":"article"},"body":"# Enabling GitHub Code Quality\n\nTurn on Code Quality to give your teams a consistent quality baseline: automatically catching, fixing, and reporting code quality issues in pull requests and on your default branch.\n\nYou can enable Code Quality for a single repository, or for every repository in an organization at once. Enabling at the organization level gives all your teams a consistent quality baseline with a single change, while enabling per repository lets you target specific projects or roll out gradually.\n\n## Prerequisites\n\n* An enterprise owner must have allowed Code Quality in your enterprise. See [Allowing use of GitHub Code Quality in your enterprise](/en/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/allow-github-code-quality-in-enterprise).\n* GitHub Actions must be enabled because Code Quality uses actions to run each CodeQL analysis.\n* To get the full benefit of the feature, your repository should include one of the languages supported for quality analysis by CodeQL. See [Supported languages](/en/code-security/concepts/code-quality/code-quality#supported-languages).\n\n## Enabling Code Quality for your repository\n\n1. On GitHub, navigate to the main page of the repository.\n\n2. Under your repository name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n\n3. In the sidebar, under \"Security\", click ** Code quality** to display the \"Code quality\" page.\n\n4. Click **Enable code quality**.\n\n5. Review the information on the Code quality page:\n\n * **Languages:** If you want to disable CodeQL analysis for any of the languages, clear the associated check box.\n * **Runner type:** If you want to use a different runner, choose **Labeled runner** and define the **Runner label**. See [Using GitHub-hosted runners](/en/actions/how-tos/manage-runners/github-hosted-runners/use-github-hosted-runners) and [Using labels with self-hosted runners](/en/actions/how-tos/manage-runners/self-hosted-runners/apply-labels).\n\n6. Click **Save changes** to save your configuration for Code Quality.\n\nIf your organization has configured caching of private registries, these will be available for code quality analysis to use to resolve dependencies. See [Giving security features access to private registries](/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries#code-quality-access-to-private-registries).\n\n## Enabling Code Quality for your organization\n\nAt the organization level, you control Code Quality with a single **Repository access** setting. This gives you granular options, from enabling every repository to targeting a specific list or a dynamic filter, so you can pilot Code Quality intentionally and roll it out at your own pace. Repositories within your selection are enabled, and repositories outside your selection are disabled.\n\nFor the available access options, and how filtering and enforcement work, see [Code Quality enablement across organizations and enterprises](/en/code-security/concepts/code-quality/enablement-at-scale#organization-level-repository-access).\n\n1. On GitHub, navigate to the main page of the organization.\n2. Under your organization name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n3. In the sidebar, under \"Security\", click ** Code quality**.\n4. Under \"Repository access\", select an option from the dropdown menu.\n * If you selected **Selected repositories...**, choose the repositories you want to enable.\n * If you selected **Matching a filter...**, define your filter.\n5. Optionally, to prevent repository administrators from changing these settings, enable **Enforce access**.\n6. If your change enables or disables Code Quality on any repositories, a \"Review enablement and billing changes\" dialog appears, showing the total number of enabled and disabled repositories and the associated costs. Review the details, then click **Confirm**.\n\nYour changes are saved automatically and begin to propagate immediately. In large organizations, it can take several minutes for the changes to apply across all repositories.\n\nIf you're rolling out the feature across many teams, we recommend you pilot on a small group and tune your quality thresholds before you enable everywhere. See [Rolling out GitHub Code Quality at scale](/en/code-security/how-tos/maintain-quality-code/roll-out-at-scale).\n\n## Next steps\n\n* **Add code coverage:** Upload reported code coverage from your test suite to see coverage results directly on pull requests. See [Setting up code coverage for your repository](/en/code-security/how-tos/maintain-quality-code/set-up-code-coverage).\n* **For your organization:** Understand the code health of your repositories at a glance. See [Exploring GitHub Code Quality results in your organization](/en/code-security/how-tos/maintain-quality-code/explore-code-quality)."}