{"meta":{"title":"Fixing code quality findings in your repository backlog","intro":"Generate autofixes for findings on the default branch of your repository, or dismiss findings that aren't relevant.","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/fix-backlog-findings","title":"Fix backlog findings"}],"documentType":"article"},"body":"# Fixing code quality findings in your repository backlog\n\nGenerate autofixes for findings on the default branch of your repository, or dismiss findings that aren't relevant.\n\n> \\[!TIP]\n> 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.\n\n## How Code Quality works on your default branch\n\nCode 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**.\n\n1. **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.\n\n2. **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.\n\n> \\[!NOTE]\n> The \"AI findings\" page for recently changed files is currently in public preview and subject to change.\n\nFor 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).\n\n## Resolving a standard finding\n\n1. Navigate to the ** Security and quality** tab of your repository.\n\n2. Click to expand ** Code quality**, then click **Standard findings**.\n\n3. 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:\n\n `is:open category:reliability severity:error`\n\n4. Findings are grouped by rule. Click a rule name to be taken to a detailed view of all findings for that rule.\n\n \n\n5. Click **Show more**, then review the explanation of the rule, what the recommended fix is, supporting code examples and references.\n\n \n\n6. To the right of an individual finding, click **Generate fix**.\n\n7. Review the diff of the proposed change. If you agree with it, click **Open pull request**.\n\n8. In the \"Commit autofix to branch\" dialog, select \"Open a pull request\", then click **Commit change**.\n\n9. 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.\n\n10. 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.\n\nTo 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).\n\n## Verifying that your code quality scores have updated\n\nAfter your autofix pull requests are merged, return to the \"Standard findings\" view to confirm that:\n\n* The number of findings has decreased.\n* The maintainability or reliability score has improved, if you resolved all findings at the current minimum severity level for that metric.\n\n## Next steps\n\n* [Fixing code quality findings in recently merged files](/en/code-security/how-tos/maintain-quality-code/fix-findings-in-recent-merges)"}