# Improve code quality at scale with GitHub

Inconsistent code quality slows every team down and adds risk you can't easily see. GitHub Code Quality catches issues before they merge and reports on code health across your organization. Follow this adoption path to evaluate the feature, run a pilot, prove its value, and roll it out at scale.

## Links

### Phase 1: Evaluate and build your business case

* [GitHub Code Quality](/en/enterprise-cloud@latest/code-security/concepts/code-quality/code-quality)

  GitHub Code Quality catches quality issues before merge, delivers one-click Copilot-powered fixes inline, and checks your code coverage.

* [GitHub Code Quality billing](/en/enterprise-cloud@latest/billing/concepts/product-billing/github-code-quality)

  In addition to standard GitHub Actions minutes, GitHub Code Quality billing has two parts: a per-committer license and AI credit usage for AI-powered features.

* [Viewing and managing GitHub Code Quality costs](/en/enterprise-cloud@latest/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.

### Phase 2: Plan your pilot

* [Code Quality enablement across organizations and enterprises](/en/enterprise-cloud@latest/code-security/concepts/code-quality/enablement-at-scale)

  GitHub Code Quality can cover one repository or thousands from a single control point, giving every team the same quality baseline and giving you the guardrails to keep it there.

* [Preventing code quality issues from reaching your default branch](/en/enterprise-cloud@latest/code-security/tutorials/improve-code-quality/catch-issues-before-merge)

  Move through Code Quality findings on your pull request, including understanding severity labels, when each finding is best fixed, delegated, or dismissed, and how those choices shape your repository's code health.

### Phase 3: Launch your pilot

* [Allowing use of GitHub Code Quality in your enterprise](/en/enterprise-cloud@latest/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/allow-github-code-quality-in-enterprise)

  Set enterprise policies for Code Quality to give organizations access while keeping repository enablement under your control.

* [Enabling GitHub Code Quality](/en/enterprise-cloud@latest/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.

* [Setting code quality thresholds for pull requests](/en/enterprise-cloud@latest/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 code coverage thresholds for pull requests](/en/enterprise-cloud@latest/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.

### Phase 4: Assess the pilot and decide

* [Exploring GitHub Code Quality results in your organization](/en/enterprise-cloud@latest/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.

* [Interpreting the code quality results for your repository](/en/enterprise-cloud@latest/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.

* [Viewing and managing GitHub Code Quality costs](/en/enterprise-cloud@latest/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.

* [Disabling GitHub Code Quality](/en/enterprise-cloud@latest/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.

### Phase 5: Scale and optimize

* [Rolling out GitHub Code Quality at scale](/en/enterprise-cloud@latest/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.

* [Exploring GitHub Code Quality results in your organization](/en/enterprise-cloud@latest/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/enterprise-cloud@latest/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.