{"meta":{"title":"Fixing code quality findings in recently merged files","intro":"Apply autofixes or delegate remediation work to Copilot for quality issues detected by AI-powered analysis of recently merged code.","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-findings-in-recent-merges","title":"Fix findings in recent merges"}],"documentType":"article"},"body":"# Fixing code quality findings in recently merged files\n\nApply autofixes or delegate remediation work to Copilot for quality issues detected by AI-powered analysis of recently merged code.\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-recent-merges-walkthrough-tip) for a guided walkthrough of reviewing and improving your repository's quality scores.\n\n## How Code Quality analyzes recently merged files\n\nCode Quality runs an AI-powered scan on recently changed files after code is merged to your default branch. This scan uses a large language model to report up to 5 findings per file in up to 5 files—across all languages, without being limited to predefined rules.\n\n> \\[!NOTE]\n> The \"AI findings\" page for recently changed files is currently in public preview and subject to change.\n\n## Viewing recent suggestions\n\n1. Navigate to the ** Security and quality** tab of your repository.\n2. Click to expand ** Code quality**, then click **AI findings**.\n\n On the **AI findings** page, each file is listed with the number of quality problems identified and when the file was pushed to the default branch. Click a file name to view the quality problems and their suggested fixes.\n\n \n\n> \\[!NOTE]\n> This view is empty if the repository is inactive or if LLM analysis could not suggest ways to improve code quality in recent pushes to the default branch.\n\n## Resolving a finding\n\nYou can delegate remediation work to Copilot or open a pull request yourself.\n\n### Delegate to Copilot\n\nYou need a Copilot license to assign work to Copilot cloud agent. Sign up for Copilot\n\n1. Select the file or files you want to include for the fix, then click **Assign to Copilot**.\n2. There is a delay while Copilot sets up the work. When the pull request is open and work is in progress, a banner is displayed with a link to the pull request.\n3. Track Copilot's work:\n * In the pull request, the summary is updated as work progresses.\n * Using the [agents page](https://github.com/copilot/agents?ref_product=copilot\\&ref_type=engagement\\&ref_style=text\\&utm_campaign=code-quality-ga-july-2026\\&utm_medium=docs\\&utm_source=docs-fix-findings-merge-agent-page) or session logs. See [Managing agent sessions](/en/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).\n\n### Open a pull request\n\n1. Click the file name to view details of the quality problems detected.\n\n2. Review the problems and suggested fixes.\n\n3. Expand the drop-down and then click **Open pull request**.\n\n \n\n4. Click **Open pull request** to open a dialog of commit options.\n\n5. Click **Commit change** to create a pull request with the fixes.\n\n> \\[!NOTE]\n> When you open a pull request yourself, you can only commit fixes to one file at a time. To fix multiple files at once, you must delegate the work to Copilot.\n\n## Further reading\n\n* [Fixing code quality findings in your repository backlog](/en/code-security/how-tos/maintain-quality-code/fix-backlog-findings)"}