Start a discussion
You can start and update a Change Stack discussion through supported provider-connected destinations. Which destinations you get depends on the connected Slack or Discord provider and the channel access it resolves â a destination you cannot see is a connection or channel-permission question, not a Change Stack setting. Updating an existing discussion is part of the same capability: a discussion is a living thread you can push back into, not a one-shot post.This is about Slack and Discord destinations specifically. Native provider discussion threads outside GitHub are not surfaced as a Change Stack discussion capability â a GitLab, Azure DevOps, or Bitbucket discussion thread on the provider itself is not something Change Stack starts or updates.
Subscribe the pull request to events
A discussion in Slack or Discord subscribes the thread to pull-request events, so it keeps up with the change without anyone re-checking the provider. When you start a discussion in Change Stack, you choose which events the thread receives. Review comments, CodeRabbit review output, and closed and merged pull requests are selected by default. You can change the selection later from Change Stack. In a Slack thread, you can also change the subscription from the thread itself:What gets delivered
A subscription delivers thirteen pull-request events, in four groups:- Lifecycle â opened, reopened, ready for review, merged, closed.
- Change â new commits or state updates, and edits to the pull requestâs own metadata or labels.
- Conversation â a pull-request comment, an inline review comment, or a resolved review thread.
- CodeRabbit and CI â a CodeRabbit comment updated, and CI failing.
Act from the thread
Eight actions run from a Slack thread. This is the complete set â anything else belongs in Change Stack itself or on the provider. These actions are Slack features; a Discord destination receives the discussion and its pull-request events, not this action set.Choose how fixes land
You can choose whether supported pull-request events trigger a fix as a commit or as a stacked pull request. The difference is where the fix lands.
For what these automated fixes contain, see Finishing Touches.
The close checklist
When work on a pull request is about to be wrapped up, CodeRabbit checks five conditions and reports each as pass, fail, or unknown. A fail is a reason to look before closing; an unknown means the condition could not be determined, which is not the same as a pass.Link expiry
Whatâs next
Review and merge
Act on the pull request directly instead of from the thread.
Snapshots
See what a discussion pins to and why a thread can fall behind the live pull request.