# Maintain quality code

Learn how to use GitHub's code security and code quality features to maintain high-quality code in your repositories.

## Links

* [Enabling GitHub Code Quality](/en/code-security/how-tos/maintain-quality-code/enable-code-quality)

  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.

* [Disabling GitHub Code Quality](/en/code-security/how-tos/maintain-quality-code/disable-code-quality)

  Stop Code Quality scans on a repository or across your organization, and know what happens to billing and your existing data before you do.

* [Rolling out GitHub Code Quality at scale](/en/code-security/how-tos/maintain-quality-code/roll-out-at-scale)

  Bring Code Quality to every team with confidence by piloting on a small group first, then expanding once your quality thresholds are tuned.

* [Setting code quality thresholds for pull requests](/en/code-security/how-tos/maintain-quality-code/set-pr-thresholds)

  Keep low-quality changes out of your codebase by using Code Quality thresholds to block pull requests that don't meet your standards.

* [Setting up code coverage for your repository](/en/code-security/how-tos/maintain-quality-code/set-up-code-coverage)

  Use built-in code coverage from Code Quality to find untested code on pull requests, without paying for or maintaining a separate third-party service.

* [Setting code coverage thresholds for pull requests](/en/code-security/how-tos/maintain-quality-code/restrict-code-coverage)

  Protect your code coverage by automatically blocking pull requests that fall below the coverage levels your team requires.

* [Fixing code quality findings on a pull request](/en/code-security/how-tos/maintain-quality-code/fix-findings-on-a-pr)

  Keep quality issues out of your default branch by applying autofixes, delegating remediation work to Copilot, or dismissing irrelevant findings.

* [Resolving a block on your pull request](/en/code-security/how-tos/maintain-quality-code/unblock-your-pr)

  Identify and resolve a code quality or coverage threshold block on your pull request so you can merge your changes.

* [Viewing code coverage on pull requests](/en/code-security/how-tos/maintain-quality-code/view-coverage-on-prs)

  Review the coverage summary posted on your pull requests to identify files with low or declining code coverage.

* [Fixing code quality findings in your repository backlog](/en/code-security/how-tos/maintain-quality-code/fix-backlog-findings)

  Generate autofixes for findings on the default branch of your repository, or dismiss findings that aren't relevant.

* [Fixing code quality findings in recently merged files](/en/code-security/how-tos/maintain-quality-code/fix-findings-in-recent-merges)

  Apply autofixes or delegate remediation work to Copilot for quality issues detected by AI-powered analysis of recently merged code.

* [Interpreting the code quality results for your repository](/en/code-security/how-tos/maintain-quality-code/interpret-results)

  Use Code Quality results to assess the maintainability and reliability of your codebase, so your teams can focus remediation where it matters most.

* [Exploring GitHub Code Quality results in your organization](/en/code-security/how-tos/maintain-quality-code/explore-code-quality)

  Use the organization-level Code Quality dashboard to spot repositories that need attention and track your organization's code health at a glance.

* [Viewing and managing GitHub Code Quality costs](/en/code-security/how-tos/maintain-quality-code/view-and-manage-cost)

  Keep your Code Quality spend predictable by seeing exactly where charges come from and using the levers that bring them down.