{"meta":{"title":"Disabling GitHub Code Quality","intro":"Stop Code Quality scans on a repository or across your organization, and know what happens to billing and your existing data before you do.","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/disable-code-quality","title":"Disable Code Quality"}],"documentType":"article"},"body":"# Disabling GitHub Code Quality\n\nStop Code Quality scans on a repository or across your organization, and know what happens to billing and your existing data before you do.\n\n## Disabling Code Quality for your repository\n\n1. On GitHub, navigate to the main page of the repository.\n2. Under your repository 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 and quality**, click ** Code quality** to display the \"Code quality\" page.\n4. Under **Code Quality analysis**, toggle from **On** to **Off**.\n\nThis stops all future Code Quality scans for that repository, along with the GitHub Actions minutes and AI credits those scans use. License charges continue for a period after you disable Code Quality. See [When billing stops](#when-billing-stops).\n\n## Disabling Code Quality for an organization\n\nDisabling at the organization level turns Code Quality off across your organization in a single change.\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 **No repositories** from the dropdown menu. This sets your organization's default to off, disabling Code Quality in every repository that follows the organization default, for both current and future repositories.\n5. To also disable Code Quality in repositories where an administrator has deliberately enabled it, and to prevent administrators from re-enabling it, turn on **Enforce access**. Without enforcement, those repositories keep Code Quality enabled.\n6. Unless you select **Let repositories decide**, a \"Review enablement and billing changes\" dialog appears, showing the total number of affected repositories. Review the details, then click **Confirm**.\n\nFor repositories affected by the organization-level change, disabling stops future scans and the metered usage they generate. Repositories that are explicitly enabled continue scanning unless you turn on **Enforce access**. License charges continue for a period after the change. See [When billing stops](#when-billing-stops).\n\nFor the full list of access options and how enforcement works, see [Code Quality enablement across organizations and enterprises](/en/code-security/concepts/code-quality/enablement-at-scale#organization-level-repository-access).\n\n## What happens to your existing data\n\nDisabling Code Quality:\n\n* Turns off future scanning. It doesn't remove your repository's code or commit history.\n* Retains your existing Code Quality data. Findings, quality scores, and history from previous scans aren't deleted when you disable Code Quality, so there's no data loss, and this data is available again if you re-enable it.\n\n## When billing stops\n\nDisabling Code Quality stops metered usage immediately, but license charges continue for a period afterwards. For an overview of what Code Quality bills for, see [GitHub Code Quality billing](/en/billing/concepts/product-billing/github-code-quality).\n\n### Metered usage stops immediately\n\nDisabling stops new scans right away, so you use no further GitHub Actions minutes or AI credits.\n\nUsage from before you disabled still bills as normal. Metered usage adds up over the course of the month and appears on your next bill.\n\n### License charges can continue\n\nDisabling Code Quality can reduce the number of licenses you use:\n\n* A committer who contributed only to repositories where you disable Code Quality no longer counts towards your license usage.\n* A committer who also contributed to another repository where Code Quality remains enabled continues to count. They stop counting 90 days after their most recent commit to an enabled repository.\n\nFor each billing period, you're charged for the highest number of licenses used at any point during that period, not the number in use at the end. Disabling Code Quality can free licenses for the next period, but it doesn't reduce the charge for the current period.\n\nCode Quality uses the same licensing model as GitHub Advanced Security. To see how the active committer count changes as people stop committing and as repositories are enabled and disabled, see [GitHub Advanced Security license billing](/en/billing/concepts/product-billing/github-advanced-security#example-showing-how-the-active-committer-count-changes-over-time).\n\n## Confirming Code Quality is off\n\nWhat confirms the change depends on the level you disabled it at.\n\n**At the organization level**, open the organization's \"Code quality\" settings page and check that **Repository access** shows your selection (for example, **No repositories**) and that **Enforce access** is on if you enforced it. The organization-level Code Quality dashboard also stops showing data for the affected repositories. See [Exploring GitHub Code Quality results in your organization](/en/code-security/how-tos/maintain-quality-code/explore-code-quality).\n\n**At the repository level**, the repository's \"Code quality\" settings page shows that Code Quality analysis is disabled. If organization or enterprise enforcement applies, the page also shows a message that a policy prevents changing the setting. No new runs start on later pull requests or pushes. On the **Actions** tab, identify existing Code Quality runs by the actor `github-code-quality` or by a run name such as \"Code Quality: push on main.\""}