> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Cards and signals
> Read a Triage card: which fields are always there, which you can turn on, what every value means, and when a signal disappears because it no longer describes the code.
export const OpenBetaBadge = ({tip = "This feature is currently in open beta. We are actively improving it based on your feedback. If you encounter any issues or have suggestions, please share them on our Discord community or visit the support page.", title = "Open Beta", cta = "Contact support", href = "/support", disabled = false}) => {
return
{title}
;
};
export const EssentialsPlanBadge = ({tip = "This feature is available on Essentials (formerly Pro), Team (formerly Pro+), Advanced, and Enterprise. Please refer to our pricing page for more information about our plans and features.", title = "Essentials Plan", cta = "Read more", href = "https://coderabbit.ai/pricing", disabled = false}) => {
return
{title}
;
};
export const GitHubBadge = ({tip = "This feature is available on GitHub and GitHub Enterprise.", title = "GitHub", cta, href, disabled = false}) => {
return
{title}
;
};
|
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:
| Field | What it shows |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Repository, number, title, author, age | Which pull request this is. |
| **Priority** | `P0`, `P1`, `P2`, `P3`, `Safe to close`, `No priority`, or `Untracked`. See [How Triage prioritizes](/triage/prioritization). |
| **Priority reasoning** | A short explanation of why this pull request is ranked where it is. Long text is shortened; **Show full priority reason** expands it, and **View priority reason** in the card menu opens all of it. |
| **Next action** | The single most useful thing to do next — see [Next action](#next-action) below. |
| **GitHub Actions** | The check-status indicator — see [Check status](#check-status). |
| **Diff size** | Lines added and removed, as `+120` / `−45`. |
| **Reviewers** | Avatars of the people on the pull request, up to three, with a `+N` when there are more. |
## 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](/triage/views-and-filters#saved-views).
| Property | What it shows |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Review state** | The provider's review decision — see [Review state](#review-state). |
| **Last activity** | `Last activity: 3 hours ago`, and so on. |
| **Change type** | `Bugfix`, `Feature`, or `Refactor`. |
| **Review guidance** | How deeply CodeRabbit suggests reviewing this: `Quick review`, `Standard review`, `Deep review`, or `Review later`. |
| **Risk** | Residual risk after CodeRabbit's review: `Low risk`, `Medium risk`, `High risk`, or `Unknown risk`. |
| **Security risk** | Security architecture risk: `Minimal`, `Low`, `Moderate`, `High`, or `Critical security risk`. Defined in [Security Architecture Review](/security/architecture-review). |
| **Issue severity** | The severity of the issues CodeRabbit raised: `High`, `Medium`, or `Low`. |
| **Blast radius** | How far the change reaches: `Low`, `Medium`, or `High blast radius`. Defined in [Security Blast Radius](/security/blast-radius). |
| **Review effort** | `Low effort`, `Medium effort`, or `High effort`, from CodeRabbit's [estimated review effort](/pr-reviews/walkthroughs#estimated-review-effort). Hover for the underlying percentage. |
**Security risk** is offered only to organizations with [CodeRabbit Security](/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](/triage/actions#close-a-pull-request) and Slack surfaces act on.
| Next action | What it means |
| ---------------------------- | ------------------------------------------------------------------------------------------------ |
| `Start review` / `Re-review` | Nobody has reviewed the current code yet. |
| `Review` | Open it in [Change Stack](/pr-reviews/change-stack) and review it. |
| `Respond to feedback` | A reviewer left something the author has not answered. |
| `Update PR` | The author needs to change the code before this can move. |
| `Fix CI` | Checks are failing. |
| `Fix merge conflicts` | The branch conflicts with its base. |
| `Refresh branch` | The branch is behind its base and needs updating. |
| `Auto Fix` | CodeRabbit can address the outstanding review feedback itself. |
| `Find reviewer` | Nobody is assigned who can review this. |
| `Ping in Slack` | A reviewer is assigned but has not acted. |
| `Review and decide` | This needs a judgment call from a maintainer, not a line-by-line review. |
| `Merge` | It is approved and nothing mechanical is blocking it. |
| `Close PR` | It appears stale or superseded. See [close candidates](/triage/prioritization#close-candidates). |
| `Follow` | There is nothing to do yet; track it in Slack instead. |
| `Open in GitHub` | Triage cannot act on this one from here. |
Most next actions are also clickable — see [Actions on a pull request](/triage/actions).
## Review state
The provider's own review decision, shown as a colored label:
| Label | Meaning |
| ------------------- | ------------------------------------------- |
| `Approved` | The pull request has the approval it needs. |
| `Changes requested` | A reviewer asked for changes. |
| `Review required` | Review is still needed before merging. |
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:
| State | Meaning |
| -------------------------------------------------- | -------------------------------------------------------------------- |
| `Passed` | Every check that reported has passed. |
| `Failed` | At least one check failed. A failure outranks work still running. |
| `In progress` | At least one check is still running. |
| `Neutral` | Checks finished without a pass or fail outcome. |
| `No checks` | The pull request reports no checks. |
| `Check status not loaded` / `Loading check status` | Triage has not fetched details yet. Open the indicator to load them. |
Open the indicator for the full list — see [View check details](/triage/actions#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:
| Signal | On a new push |
| -------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Change type, issue severity, blast radius, security risk | Hidden until CodeRabbit reviews the new commit. |
| Review effort, risk, review guidance | Kept — these describe the change as a whole and survive a push. |
| Review state | Reflects the provider. An approval that no longer covers the latest commit stops being labeled. |
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
See how these signals combine into a priority, and how to override one when you disagree.
Filter and group the queue by any of the signals on this page.
Act on a card without leaving the queue — review, repair, reassign, or close.