Advanced Features
PullPro includes several advanced features that give you greater control over how pull requests are managed within Slack. These features are designed to provide flexibility for teams with specific workflows, including moving PRs between channels and holding one back from review until it merges.
Move PRs Between Channels
Sometimes a pull request may be posted in the wrong Slack channel, or you may decide to move it based on team discussions. PullPro allows you to easily move a PR from one Slack channel to another using a simple Slack message shortcut.
How to Move PRs Between Channels
- Locate the PR post in the current Slack channel.
- Click the message options button (the three dots).
- Select the Move to another channel option.
- Choose the destination Slack channel from the dropdown list.
Once the PR is moved, all future notifications and updates for that PR will be sent to the new channel. Any reminders for the PR in the previous channel will be marked as resolved.
Post When Merged
Some pull requests do not need the team's attention before they merge — a version bump, a generated file, a small internal change. A channel can hold those back while they are open: choose the labels that mark them in the channel's Post when merged routing setting, and a pull request carrying any of them is not posted there for review.
Steps
- In the PullPro app home tab, open the channel's settings and choose Post when merged under Routing.
- Pick the labels that mean "no review needed" — for example Dependabot's
dependencies, or your team's ownno review. Labels match by name in any repository and ignore case. - On GitHub, apply one of those labels to a pull request.
While the pull request is open it is not posted to that channel and it sends no review reminders there. Once it merges, PullPro posts it, so the work still shows up and still counts towards your metrics. If the label comes off before it merges, it's posted then, the same way a newly opened pull request is.
Posting a pull request yourself overrides the hold: /pr, Move to another channel and the Post now
button in the failed-checks message all post it to the channel even while it carries one of these labels.
The setting is per channel: a pull request held in one channel is still posted for review in any other channel
it routes to. Channels set up before this setting existed already hold skip review, so that label keeps
working where your team used it. PullPro doesn't create labels in your repositories — use ones you
already have. See how the routing rules combine.