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.

How Code Quality works on pull requests

When you open a pull request, Code Quality uses CodeQL to perform a rule-based scan of your changes and posts findings as comments by github-code-quality[bot]. Each finding includes 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.

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].
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 it by clicking Dismiss 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.

Delegating remediation work to Copilot

If you have a Copilot license, you can delegate the remediation work to Copilot cloud agent. Comment on the pull request mentioning @Copilot and request that Copilot fix the detected issues.

Copilot responds with an eyes emoji (👀) to your comment, starts a new agent session, and opens a pull request with the necessary fixes.

You can track Copilot cloud agent's work:

• In the pull request, the summary is updated as work progresses.
• Using the agents page or session logs, see Managing agent sessions.

You need a Copilot license to invoke Copilot cloud agent.
Sign up for Copilot

Next steps

• Viewing code coverage on pull requests