Skip to main content
GitHub
Qodo provides automatic CI feedback when a pull request contains failed checks. When a CI failure is detected, Qodo analyzes the results and surfaces structured, actionable information directly in the pull request to help you quickly understand and resolve the issue. The CI feedback includes:
  • Failed stage – the pipeline stage where the failure occurred
  • Failed test name – the specific test or job that failed
  • Failure summary – a concise explanation of what went wrong
  • Relevant error logs – extracted log output to aid debugging
This feedback helps reduce context switching by keeping CI failure analysis inside the pull request, where you are already working.

​
Using CI feedback in pull requests

​
Manual usage

Comment on the PR:
Where:
  • {repo_name} is the name of the repository.
  • {run_number} is the run number of the failed check.
  • {job_number} is the job number of the failed check.

​
Disabling the tool from running automatically

If you want to disable the tool from running automatically, add the following to the configuration file:

​
Configuration options

Configure the checks tool by setting configurations under the checks part in your configuration file. Example:
PR comment showing a failed CI check with details from Qodo
Expanded CI check failure details shown in a pull request comment
Example output of CI failure feedback displayed as a Qodo comment on a pull request