# 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](/es/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 **revisión de código 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 [Sobre la revisión de código de GitHub Copilot](/es/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
Como alternativa, si tiene una Copilot licencia, puede delegar el trabajo de corrección en agente en la nube de Copilot. Haga un comentario en la solicitud de incorporación de cambios mencionando `@Copilot` y solicite que Copilot corrija los problemas detectados.
Copilot responde con un emoji de ojos (👀) a tu comentario, inicia una nueva sesión del agente y abre un pull request con las correcciones necesarias.
Puede hacer seguimiento del trabajo de agente en la nube de Copilot.
* En el pull request, el resumen se actualiza conforme avanza el trabajo.
* Utilizando la [página de agentes](https://github.com/copilot/agents?ref_product=copilot\&ref_type=engagement\&ref_style=text) o los registros de sesión: consulte [Gestión de sesiones del agente](/es/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).
Necesita una Copilot licencia para invocar agente en la nube de Copilot. Regístrese para Copilot
## Next steps
* [Viewing code coverage on pull requests](/es/code-security/how-tos/maintain-quality-code/view-coverage-on-prs)