How it works
When a pull request is opened or updated, CodeRabbit waits for GitHub Checks to finish and then reads their output. Any failures are analyzed and surfaced as inline review comments on the relevant lines of code, alongside suggested fixes. This integration covers a broad range of check types including:- Build failures (Docker, Node.js, Java, Python, Go, etc.)
- Test failures (unit, integration, end-to-end)
- Security scan findings (SAST, DAST, container scanning)
- Infrastructure-as-code validation (Terraform, Kubernetes, Ansible)
- Linter output from tools running in your CI pipeline
Configuration
GitHub Checks integration is enabled by default. You can configure whether it is enabled using your.coderabbit.yaml file or the CodeRabbit web UI.
- .coderabbit.yaml
- Web UI
.coderabbit.yaml
Options
When CodeRabbit skips GitHub Checks
CodeRabbit skips the GitHub Checks integration when:enabledis set tofalse.- The repository is not hosted on GitHub.
- No GitHub Checks data is available for the review.
What’s next
CI/CD pipeline analysis
Learn how CodeRabbit reads CI/CD pipeline failures and posts inline remediation suggestions across GitHub Actions, GitLab, CircleCI, and Azure DevOps.
All supported tools
Browse the complete list of linters, security analyzers, and CI/CD integrations available in CodeRabbit.
Configuration reference
Full reference for all available options, including how to enable, disable, and tune individual tools.