Skip to main content
| A team opens more pull requests than it has hours to review them, and some of those pull requests are written by coding agents. A Git provider shows them one repository at a time, in a list that doesn’t say which change matters most, which one is waiting on you, or which one should be closed. CodeRabbit Triage puts the open pull requests from the repositories you can access into one queue, ordered by what each one needs next and what acting on it is worth. Each card answers two questions: how much the pull request is worth acting on compared to everything else in the queue, and what has to happen for it to move. You can see at once whether you have to move or someone else does. Triage doesn’t stop at ranking. With Triage rules, it also gets pull requests ready before you open them: rules repair failed CI checks, address review feedback, merge low-risk changes, close stale pull requests after notice, and send Slack reminders. That leaves your time for the changes that need your judgment. The actions a rule can run depend on your Git provider.
Triage queue in the CodeRabbit web app showing the Requires my action view. The top card, Add teammate invitations with roles, is P0 because it blocks Friday's invitations launch, with passing checks and the next action Review this pull request in Change Stack. Below it are lower-priority cards for other pull requests, each with its own next action.

The Requires my action view, with example data: each pull request with its priority, the reason for it, and its next action

Triage is built for the person who has more pull requests in front of them than review hours: a reviewer, a code owner, a maintainer, or a team lead deciding what to pick up now.

What you’ll use Triage for

  • Focus on what needs your attention now. Land on Requires my action to see just the pull requests you’re on, ranked so the most consequential is at the top.
  • See whether the ball is in your court. The next action on each card tells you whether you have to move (Update PR, Respond to feedback, Merge) or someone else does (Ping in Slack, Find reviewer).
  • Clear out stale work. Close candidates surfaces pull requests that duplicate, supersede, or have drifted so far they no longer apply — with a close button.
  • Take the next step without leaving the queue. Start a review, fix CI, resolve conflicts, ping a reviewer in Slack, or close a pull request from the card itself. See Actions on a pull request.
  • Get the queue to come to you. A scheduled Slack digest brings the top of your queue to you once or twice a day; get updates about specific pull requests in your Slack Home or a chosen conversation. See Triage in Slack.
  • Automate repeatable work. Use Triage rules to merge ready changes, close stale PRs after notice, repair CI and feedback, or send recurring Slack reminders. Available actions depend on your Git provider.

Who can use Triage

Triage is available on the Team plan and higher, and free for open-source organizations on their public repositories. It works with GitHub, GitLab, Bitbucket, and Azure DevOps, and GitLab support is in beta. See Requirements and FAQ for the full requirements and what needs a Review seat. Open Triage at app.coderabbit.ai/triage, or from Triage in the app sidebar. If the queue is empty or out of date, or an action is refused, see Troubleshooting Triage.

What’s next

Your Triage view

Learn what each field on a card means, and how to filter, group, and save your own view of the queue.

How Triage prioritizes

Understand the evidence and precedence behind a priority, and when it’s allowed to change.

Actions on a pull request

See what you can do directly from a card, and which actions need a Review seat.