GitHub Checks

How CodeRabbit integrates with GitHub Checks to surface CI/CD pipeline failures and provide automated remediation suggestions on every pull request.

GitHub Checks is a CodeRabbit integration that reads the results of your GitHub Actions workflows and other CI/CD checks and incorporates them into the pull request review. When a check fails, CodeRabbit analyzes the failure logs and posts inline comments with remediation suggestions.

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

enabled · boolean · default: true

Enable GitHub Checks: Enable integration, defaults to true

.coderabbit.yaml

.coderabbit.yaml

reviews:
  tools:
    github-checks:
      enabled: true

Web UI

In your organization or repository settings, go to Reviews → Tools and turn the tool on or off with its toggle.

When CodeRabbit skips GitHub Checks

CodeRabbit skips the GitHub Checks integration when:

• enabled is set to false.
• The repository is not hosted on GitHub.
• No GitHub Checks data is available for the review.

After the bounded GitHub Actions log reader is deployed, CodeRabbit will retain up to 4 MiB from the end of each decompressed entry and analyze the final complete-line segment of up to 2,097,152 characters. A failure earlier in the log can be omitted from the check output, and an oversized single-line log can produce no check details. Workflow archives will be limited to 32 MiB of compressed data, and each entry will be limited to 32 MiB of decompressed data. When a limit is exceeded, CodeRabbit may use GitHub Checks output as fallback context. Displayed check text is capped at 65,535 characters, and secret redaction still runs before output.

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.