Skip to main content
| A card is one open pull request. It carries three kinds of information, and knowing which is which tells you how much to trust each one:
  • Provider facts — the title, the author, the review decision, the check results. CodeRabbit reads these from GitHub.
  • Review signals — risk, blast radius, issue severity, review effort. CodeRabbit produced these while reviewing a specific commit, so they can be withdrawn when a newer commit lands.
  • Triage’s own judgment — the priority, the next action, and the reasoning text. These are derived from both of the above.

​
What is always on a card

These fields cannot be turned off:

​
What you can turn on

Open Display, then Display properties, and toggle any of these. Your choice is remembered per view and is stored in saved views.
Security risk is offered only to organizations with CodeRabbit Security review enabled. Organizations without it see Risk on by default instead.

​
Next action

Every card names one next action — not a list of options, the single step Triage believes moves this pull request forward. It is also what the safe-close and Slack surfaces act on. Most next actions are also clickable — see Actions on a pull request.

​
Review state

The provider’s own review decision, shown as a colored label: Hover Approved or Changes requested to see how many reviews are behind the label. When an approval no longer covers the latest commit, no label is shown rather than a stale one.

​
Check status

The GitHub Actions indicator summarizes the latest check run: Open the indicator for the full list — see View check details.
A visible failure is reliable evidence. The absence of one is weaker: a check list can be truncated or time out while loading, and the card does not distinguish “all checks passed” from “as many checks as we could read passed”. Before merging on a green indicator, confirm in the provider.

​
Merge conflicts and base drift

Triage tracks whether a branch conflicts with its base or has simply fallen behind it, but there is no separate conflict badge on the card. You see it through the next action instead — Fix merge conflicts for a real conflict, Refresh branch for a branch that is only behind — and through the repair action in the card menu.

​
Tracked and untracked

A pull request that CodeRabbit has no review context for is shown as Untracked. It appears in the queue and you can still act on it, but it carries no review signals, no review guidance, and no calculated priority. Repositories that CodeRabbit does not review produce untracked cards.

​
Signal freshness

Review signals describe the commit CodeRabbit reviewed. When an author pushes a newer reviewable commit, Triage withdraws the signals that would be misleading rather than showing them against code they no longer describe:
A card carries one freshness timestamp, but its fields arrive from different sources at different moments. A recent timestamp means something on the card was updated recently — not that every field on it was.

​
What’s next

How Triage prioritizes

See how these signals combine into a priority, and how to override one when you disagree.

Views, filters, and layout

Filter and group the queue by any of the signals on this page.

Actions on a pull request

Act on a card without leaving the queue — review, repair, reassign, or close.