# 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](/ja/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 **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 [GitHub Copilotによるコードレビューについて](/ja/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
または、 Copilot ライセンスがある場合は、修復作業を Copilot クラウドエージェントに委任できます。 pull request にコメントし、`@Copilot`に言及していることを明示し、Copilotに検出された問題の修正を要求します。
Copilot は、コメントに目の絵文字 (👀) で応答し、新しいエージェント セッションを開始し、必要な修正を含む pull request を開きます。
Copilot クラウドエージェントの作業を追跡できます。
* pull request では、作業の進行状況に応じて概要が更新されます。
* [エージェント ページ](https://github.com/copilot/agents?ref_product=copilot\&ref_type=engagement\&ref_style=text)またはセッション ログの使用については、[エージェント セッションの管理](/ja/enterprise-cloud@latest/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents) を参照してください。
Copilotを呼び出すには、Copilot クラウドエージェント ライセンスが必要です。 サインアップ Copilot
## Next steps
* [Viewing code coverage on pull requests](/ja/enterprise-cloud@latest/code-security/how-tos/maintain-quality-code/view-coverage-on-prs)