Built-in views
The rail down the left of the queue holds your views. Three are built in:
Every view is limited to pull requests that are open and tracked by CodeRabbit, in repositories you can access.
There is no separate “authored by me” view. Requires my action is deliberately the union of your authoring and your reviewing, because in practice you want one queue rather than two. To narrow it to just your own pull requests, filter by PR author.
Search and filters
Search — the box at the top of the queue matches pull request titles,owner/repository names, and pull request references like #4312.
Filters — open Filter to narrow by any of these. Each is a multi-select: choosing several values matches any of them.
Clear filters removes all of them at once.
Filters live in the URL, not in your account. That means a filtered queue is a link you can paste to a colleague — and that filters are not restored when you come back later. To keep a combination, save the view.
Grouping and ordering
Open Display to arrange the queue. Grouping splits it into labelled sections, and Sub-grouping splits those again by a second field. Both offer:
Ordering sorts within each group by Priority, Last activity, Created, PR number, or Title, ascending or descending.
Grouping and ordering are applied to the whole queue before it is paged, so page two continues exactly where page one stopped rather than re-sorting a slice.
Sections can be collapsed, and a collapsed section stays collapsed as you move around. Hold Alt while collapsing to collapse every section at once.
List and board
List is one row per pull request, 100 to a page — the denser view, and the better one for reading down a ranking. Board is a column per group, 20 cards to a column, starting with six columns and loading more on request — the better one for seeing the shape of the queue, such as how much is waiting on authors versus waiting on reviewers. Switching layout does not change which pull requests are in the queue, only how they are drawn.Card properties
Display > Display properties turns individual card fields on and off. Some fields are always shown and are not listed there. The full set, and what each one means, is in Cards and signals.Saved views
A saved view captures a whole working setup — filters, layout, grouping, ordering, visible card properties, and which sections are collapsed — under a name and an icon of your choosing. Saved views appear in the left rail below the built-in ones.- Save current view stores what you are looking at now.
- Update from current overwrites a saved view with your current setup; Rename and Delete do what they say.
- Saved views are personal. They belong to you within one organization and are not shared with your team.
- You can keep 50 of them, with names up to 100 characters. At the limit, Save current view is disabled until you delete one.
A saved view stores the definition, not the result. Reopening it re-runs its filters against the current queue, so it shows you what matches today — not the pull requests that happened to be there when you saved it.
Team views
When team views are enabled for your organization, the rail carries a Teams section listing the GitHub teams you belong to. Selecting one scopes the queue to the pull requests where that team is a requested reviewer — the team’s review backlog, rather than everything its members happen to be involved in. Team views work inside All PRs only. Your team memberships are read from your own GitHub account and refreshed periodically; if your GitHub authorization has lapsed, Triage asks you to reconnect rather than showing you a partial list.Team views are rolling out per organization, so the Teams section may not be there yet.
Focus lanes
Grouping by Focus splits the queue into two lanes:
“Capacity” is not a setting anyone configures. Triage measures each author’s recent throughput — how much review-complexity their merged pull requests carried over the last 30 days — and fills Now from the top of the ranked queue until that budget is spent. Once something does not fit, everything after it goes to Next, including smaller work that technically would have fitted; the lane boundary is a line in the ranking, not a knapsack.
Because the ranking is different for each person, the same pull request can be Now for its author and Next for one of its reviewers. That is intended: each of you has a different queue and a different budget.
What’s next
Cards and signals
Look up what every card property means before you decide which ones to show.
Actions on a pull request
Act on the queue you just built, without leaving it.
How Triage prioritizes
Understand the ranking that decides the order inside every group.