Settings & Best practices

Organizations have all sorts of needs, some are different from team to team. Configure Pullpo to fit your specific needs in the settings page. However, there are some common best practices that you might want to implement to get the most out of Pullpo.

Settings

Here's an overview of the available settings for the Pullpo - PR Channels tool:

Title	Description	Default value
Full bidirectionality	When enabled, messages that are not thread responses will also be sent to the pull request discussion.	Off
Public channels	Create public channels insted of private on every pull request.	Private
Draft PRs	Create channels also on draft pull requests.	Off
AI Summarizer	Generate an AI analysis of the pull request on PR channels.	Off
Auto-archive channels	Archive channels when the associated pull request is merged or closed.	On
Title template	PR channel titles follow the format specified in this template.	_pr_$REPONAME$_$PRTITLE$
Ignored terms	Don't create channels for pull requests with these terms in the title.	Empty
Ignored labels	Don't create channels for pull requests with these labels.	Empty
Ignored repositories	Specify a list of repositories whose pull requests should (or shouldn't) create PR channels.	None excluded
Notifications	Define the type of messages and alerts you want to be sent in the channel.	All

If your organization is only interested in Pullpo - Insights it can turn off the PR Channels tool altogether.

Best practices

Authorize impersonation

When sending synced messages through PR channels, users that still haven't granted impersonation permissions will be prompted to do so. Allowing impersonation will improve the overall notification experience.

Synced messages will still contain a 'Sent via Pullpo' tag to avoid confusion.

Advantages

Stop getting Slack notifications for your own PR comments or actions.
Continue to get notified when teammates respond to your threads.
Write or edit comments in the PR discussion as authored by you, when interacting via Slack.
Write or edit comments in Slack as authored by you, when interacting via the PR discussion.
Enable approving pull requests directly form a Slack slash command.

Users who choose not to opt in to this improved notification system can snooze impersonation requests and continue using PR Channels as usual.

Git ↔ Slack sync limitations

On GitHub, top-level comments on pull requests do not allow for threaded conversations. We developed a workaround called GitHub PR Issue Threads that you may consider trying out.
On GitLab, there's no webhook event when a comment is edited or deleted, so Pullpo can't update the corresponding Slack message. It does work the other way around.
On GitLab, there's no webhook event when a review is re-requested, so the corresponding alert is not sent through the PR channel.

Arrange Slack sections

Slack workspaces on a paid plan can organize channels into custom sections. However, due to Slack limitations, Pullpo's bot can only create PR channels in the default 'Channels' section.

We recommend keeping your own channels in a dedicated section. This way, new PR channels will be automatically grouped under the default section you'll avoid clutter.

Define Squad channels

You can assign specific Slack channels to squads (groups of members who regularly collaborate). These channels can receive:

Weekly engineering summaries (via the Insights product)

PR Status Messages that update in real time to show each reviewer's progress on a pull request.

And for teams where reviewers self-assign, squad channels can also receive recurring pick-up reminders for PRs that are still waiting to be reviewed.