Slack delivery requires a connected Slack workspace and a link between your CodeRabbit account and your Slack account. Setting that up is covered in CodeRabbit Agent for Slack. It is also rolling out gradually, so it may not be switched on for your organization yet.
The PR digest
The digest is a scheduled message listing the pull requests most worth your attention right now, scoped to what you can see and to your part in each one.Schedule
Set the cadence in Follow settings on the Triage page:
If you have quiet hours configured, the first digest arrives when your quiet hours end rather than at 9:00. Follow settings shows exactly when the next one is due, in your timezone.
What it contains
Up to four sections, in this order, with the most urgent pull requests in each:
Each pull request carries its title, its priority reasoning, its age, and buttons for the obvious next step â approve, request changes, close, or ask CodeRabbit to repair it. A section you have nothing in is left out entirely.
The digest is a summary, not an inventory. It shows a few pull requests per section and tells you how many more there are, with a link back into Triage for the rest.
No digest is sent when you have nothing waiting. Triage does not send an all-clear. An unchanged digest is also not re-sent, so a second delivery means something actually moved.
If your GitHub authorization lapses
The digest is scoped to repositories you can access, so it needs your GitHub authorization to build. When that authorization expires, Triage sends a single message asking you to reconnect GitHub instead of sending a partial digest that quietly omits repositories.Reviewer requests
When you ask someone to review a pull request from Triage, and their GitHub account is linked to Slack, they get a direct message from you: who is asking, the pull request, CodeRabbitâs summary of it, and an Approve button. Reviewer requests are only ever sent because a person asked for one. Triage does not send unsolicited review pings. The same requests are collected under Review requests in the CodeRabbit appâs Slack Home tab, so a reviewer can see everything waiting for them in one place rather than hunting through direct messages. Each one offers Approve, Comment, and Ignore. The Home tab is rebuilt with every new request, so it always shows the current set.Linking identities
Sending a request to Slack requires knowing which Slack account belongs to which GitHub account. When Triage is confident of the match it uses it; when more than one Slack account could be the right person, it asks you to confirm before sending, rather than messaging the wrong colleague. Reviewers who have turned reviewer notifications off do not receive these messages, and Triage tells you so instead of failing silently.Acting from Slack
The buttons on a digest or a review request run against GitHub as you, using your own authorization:
If CodeRabbit has no current GitHub authorization for you, the button tells you to connect GitHub rather than failing quietly.
Follow a pull request
Follow on a card sends that pull requestâs activity to a Slack channel or direct message of your choosing, in its own thread. Use it for a change you want to track without it being your review. Choose Follow from the cardâs action menu, pick a channel or send it to yourself, and choose whether to use your default event settings or pick specific events. Following a pull request needs a tracked, open pull request, a connected Slack workspace, your linked Slack identity, and CodeRabbit access to the channel you pick. To stop, open Follow settings and choose Unfollow.Whatâs next
CodeRabbit Agent for Slack
Connect a Slack workspace and see everything else CodeRabbit can do there.
Actions on a pull request
Do the same things from the queue, with the full context of the card in front of you.
Troubleshooting Triage
Find out why a digest did not arrive or a Slack message could not be delivered.