# Fixing code quality findings on a pull request
Keep quality issues out of your default branch by applying autofixes, delegating remediation work to Copilot, or dismissing irrelevant findings.
> \[!TIP]
> If you're new to Code Quality, see [Preventing code quality issues from reaching your default branch](/fr/enterprise-cloud@latest/code-security/tutorials/improve-code-quality/catch-issues-before-merge?utm_campaign=code-quality-ga-july-2026\&utm_medium=docs\&utm_source=docs-fix-pr-findings-walkthrough-tip) for a guided walkthrough of how Code Quality works on pull requests.
## How Code Quality works on pull requests
When you open a pull request, Code Quality runs **two types of analysis** and posts findings as comments on the pull request.
1. **`github-code-quality[bot]` findings**: Code Quality uses CodeQL to perform a rule-based scan of your changes. These findings are posted as comments by `github-code-quality[bot]` and include a suggested autofix. Findings are labeled by severity (**Error**, **Warning**, **Note**), and administrators can set quality gates to block merges based on the severity of these findings.
2. **Copilot findings**: If your organization has Copilot licenses and AI features are enabled for your enterprise, Code Quality uses **révision du code Copilot** to identify quality issues that rules-based analysis may not detect. These findings are posted as comments by **Copilot**, and include a suggested autofix. See [À propos de la révision de code avec GitHub Copilot](/fr/enterprise-cloud@latest/copilot/concepts/agents/code-review).
## Resolving a finding
1. On GitHub, navigate to your open pull request.
2. On the **Files Changed** tab, scroll to a comment left by **`github-code-quality[bot]`** or **Copilot**.
3. Carefully review the comment and the suggested autofix for logic, security, and style.
4. If you agree with the suggestion and you want to apply the fix, click **Commit suggestion**, or **Add suggestion to batch**.
5. Alternatively, if the finding isn't relevant or actionable, you can dismiss the finding. 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.
* For comments left by `github-code-quality[bot]`, click **Dismiss finding**.
* For comments left by Copilot, click **Resolve**.
## Delegating remediation work to Copilot
Sinon, si vous disposez d’une Copilot licence, vous pouvez déléguer le travail de correction à Agent cloud Copilot. Commentez la pull request en mentionnant `@Copilot` et demandez à Copilot de corriger les problèmes détectés.
Copilot répond avec un émoji de yeux (👀) à votre commentaire, démarre une nouvelle session pour l'agent et ouvre un pull request avec les correctifs nécessaires.
Vous pouvez suivre Agent cloud Copilotle travail :
* Dans le pull request, le résumé est mis à jour à mesure de l'avancement du travail.
* À l’aide de la [page des agents](https://github.com/copilot/agents?ref_product=copilot\&ref_type=engagement\&ref_style=text) ou des journaux de session, consultez [Gestion des sessions des agents](/fr/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).
Vous avez besoin d’une Copilot licence pour appeler Agent cloud Copilot. S’inscrire Copilot
## Next steps
* [Viewing code coverage on pull requests](/fr/enterprise-cloud@latest/code-security/how-tos/maintain-quality-code/view-coverage-on-prs)