Thanks to visit codestin.com
Credit goes to docs.coderabbit.ai

Skip to main content
| CodeRabbit Triage is a single queue of every open pull request your organization is tracking, ordered by what each one needs next and what acting on it is worth. It 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. Triage is a Team-plan, GitHub Cloud, open-beta product. See Requirements and FAQ for the full eligibility matrix and what needs a Review seat. Open Triage at app.coderabbit.ai/triage, or from Triage in the app sidebar.

​
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; follow specific pull requests for real-time updates. See Triage in Slack.

​
Where to start

​
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.