# Fixing code quality findings in your repository backlog
Generate autofixes for findings on the default branch of your repository, or dismiss findings that aren't relevant.
> \[!TIP]
> If you're new to Code Quality, see [Raising your repository's code quality score](/en/code-security/tutorials/improve-code-quality/raise-your-quality-rating?utm_campaign=code-quality-ga-july-2026\&utm_medium=docs\&utm_source=docs-fix-backlog-walkthrough-tip) for a guided walkthrough of reviewing and improving your repository's quality scores.
## How Code Quality works on your default branch
Code Quality scans your default branch and reports findings on "Code quality" pages on the ** Security and quality** tab of your repository. It runs **two types of analysis**.
1. **Standard findings**: Code Quality uses CodeQL to perform a deterministic, rules-based scan of your default branch. Finding are grouped by rule and language, labeled by severity (**Error**, **Warning**, **Note**), and each includes a suggested autofix.
2. **AI findings**: Code Quality uses AI-powered analysis to identify quality issues in the files most recently pushed to your default branch, including issues that rule-based analysis may not detect - such as best practices, naming conventions, or design considerations.
> \[!NOTE]
> The "AI findings" page for recently changed files is currently in public preview and subject to change.
For information on resolving AI findings, see [Fixing code quality findings in recently merged files](/en/code-security/how-tos/maintain-quality-code/fix-findings-in-recent-merges).
## Resolving standard findings
You can resolve findings individually or assign multiple findings to Copilot.
> \[!NOTE]
> Agentic Autofix for GitHub Code Quality backlog findings is currently in public preview and subject to change.
### Resolving a single finding
1. Navigate to the ** Security and quality** tab of your repository.
2. Click to expand ** Code quality**, then click **Standard findings**.
3. Use the dashboard filters to focus on the findings most likely to affect your quality scores. For example, to see all "Error"-level findings for "Reliability", set the filter to:
`is:open category:reliability severity:error`
4. Findings are grouped by rule. Click a rule name to be taken to a detailed view of all findings for that rule.
5. Click **Show more**, then review the explanation of the rule, what the recommended fix is, supporting code examples and references.
6. To the right of an individual finding, click **Assign to Copilot**. Assigning a finding to Copilot consumes AI credits.
7. Review the draft pull request that Copilot opens with a fix for the finding.
8. When the autofix pull request is ready for review, change its status from "Draft" to "Ready for review", and wait for CI checks to pass before merging.
9. Alternatively, if a finding isn't relevant or actionable, click **Dismiss**. For example, you might dismiss a finding that is in legacy code no longer maintained, is a known exception to your team's coding standards, or is a false positive that doesn't pose a real quality risk.
To raise a maintainability or reliability score, you must resolve every finding at the highest severity level currently affecting that metric. See [Metrics and scores reference](/en/code-security/reference/code-quality/metrics-and-ratings).
### Assigning multiple findings to Copilot
If you have many findings for a rule and want to remediate them efficiently, you can select these findings in bulk and assign them to Copilot for agentic remediation. Copilot will open a pull request with fixes for the selected findings.
You don't need a Copilot license to use this feature, but your enterprise owner must allow Code Quality for your organization. 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).
For the best results, start with a single rule that has many high-severity findings. This lets you validate the quality of the autofixes on a cohesive set of changes before expanding to other rules.
1. Navigate to the ** Security and quality** tab of your repository.
2. Click to expand ** Code quality**, then click **Standard findings**.
3. Select the findings you want to remediate. You can select up to 25 findings per page, one page at a time.
4. Click **Assign to Copilot**.
5. Copilot will open a pull request with fixes for the selected findings. Review the pull request carefully before merging.
## Verifying that your code quality scores have updated
After your autofix pull requests are merged, return to the "Standard findings" view to confirm that:
* The number of findings has decreased.
* The maintainability or reliability score has improved, if you resolved all findings at the current minimum severity level for that metric.
## Next steps
* [Fixing code quality findings in recently merged files](/en/code-security/how-tos/maintain-quality-code/fix-findings-in-recent-merges)