> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cubic.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack PR channels

> Open a private Slack channel for a pull request with its author and reviewers.

A PR channel is a private Slack channel for a single pull request. It brings the PR author and
reviewers together and posts the pull request's GitHub activity and cubic reviews as they happen.

## Requirements

* Connect Slack in [Settings > Integrations](https://www.cubic.dev/settings?tab=integrations\&integration=slack)
  so cubic can send you PR notifications.
* Link your cubic account to GitHub.
* For a private repository, you need access to the repository.

## Open a PR channel

1. Find a cubic Slack notification about the pull request, such as a PR update or the message
   cubic sends when a review finishes.
2. Click **Open PR channel**.

cubic replies in the notification's thread while it sets up the channel, then links to it. If the
channel already exists, cubic adds you to it.

The button appears when the pull request already has a channel, or when there is at least one other
person cubic can invite. cubic decides this when it sends the notification, so older messages keep
the button state they were sent with.

## Who is invited

When cubic creates the channel, it invites:

* The PR author
* Requested reviewers
* Up to five members of each requested GitHub team
* You

cubic invites a person only when it can match their GitHub account to a Slack user in your
workspace, and only if they can access the repository when it is private. After the channel is
created, cubic sends you a private summary of anyone it could not invite. Add them to the channel
yourself.

cubic invites people once, when it creates the channel. Reviewers added to the pull request later
are not invited automatically, and clicking **Open PR channel** on an existing channel only adds
you.

## What cubic posts

The channel starts with the pull request's title, linked to the PR, and cubic's summary from the PR
description.

After that, cubic posts:

* Pull request updates, reviews, review comments, and PR comments from GitHub
* Review results, with the number of issues cubic found

Only activity after the channel is created is posted. Long updates are shortened, with a link back
to the pull request.

## Archiving and reopening

cubic archives the channel when the pull request is merged or closed. Reopening the pull request
does not unarchive it.

To bring the channel back, click **Open PR channel** again on a notification for the pull request.
cubic unarchives the same channel, even if the pull request is still closed. If Slack does not
allow cubic to unarchive it, ask a channel member to unarchive it in Slack.

## Channel names

Channels are named `pr-<repository>-<number>-<title>`, using the first words of the pull request
title. If the name is taken, cubic adds a suffix.
