Post-merge actions automate changelogs, tickets, and Slack summaries

Post-Merge Actions

|

CodeRabbit can now run automated follow-up work after a pull request is merged. Define Post-Merge Actions as natural-language instructions. For example, append a changelog entry, file a Linear or Jira ticket, open a GitHub issue, or post a Slack summary. CodeRabbit executes them agentically against the merged changes.

Each enabled action is previewed as a checkbox in the 🚀 Post-Merge Actions section of the PR walkthrough, checked when CodeRabbit judges it applicable to the change. The author or a reviewer can skip all actions, or named actions, with @coderabbitai skip post-merge actions (optionally --name "...") before merging. On merge into the default branch, CodeRabbit runs the still-checked actions and posts a single result comment. Code-changing actions land as a follow-up pull request.

Configure up to five actions per organization from Settings → Post-merge actions or in .coderabbit.yaml under reviews.post_merge_actions. See the Post-Merge Actions documentation for details.