How to keep pull requests moving in chat.
Short, practical pages for the search queries teams actually type — then deep links into the pairing docs, product model, and pricing.
4 guides
Connect your forge to chat
Start with the GitHub or GitLab and Slack or Discord pairing your team already uses.
GitHub pull request notifications in Slack
Route each repository to the right Slack channel, keep one living thread per PR, and mention mapped reviewers.
Read guideGitHub pull request notifications in Discord
Route GitHub pull requests to a Discord channel, open one public thread per request, and keep reviews and checks together.
Read guideGitLab merge request notifications in Slack
Send GitLab merge request activity into focused Slack threads, with mapped reviewer mentions and pipeline changes beside the request.
Read guideGitLab merge request notifications in Discord
Watch GitLab projects, open one Discord thread per MR, and keep pipeline failure and recovery beside the request.
Read guide4 guides
Keep reviews moving
Route work clearly, nudge it once when it stalls, and give the team one daily queue to act on.
Route pull requests to chat by repository or label
Use routes to separate repositories, labels, authors, branches, and review events across Slack and Discord without a notification free-for-all.
Read guideStale pull request reminders in Slack and Discord
ForgeRelay can remind mapped reviewers once after a configurable wait, without flooding the channel.
Read guidePull request review reminders for Slack and Discord
Set a review reminder that reaches mapped reviewers in Slack or Discord after a request waits too long, then stays quiet.
Read guideDaily pull request review digest for Slack and Discord
Schedule a review digest for awaiting, failing, blocked, stale, or ready-to-merge work, then open the queue when something needs attention.
Read guide2 guides
Make delivery visible
Keep CI failures, recoveries, and direct-to-main work in the conversations that need them.
Send CI failures and recoveries to Slack or Discord
Keep failing checks, jobs, and recoveries attached to the pull or merge request conversation instead of scattering alerts across chat.
Read guideCommit digests for main-branch pushes
Commit digest routes post one filtered digest per push to a watched branch in Slack or Discord.
Read guidePrefer the pairing pages?
Each forge-to-chat combination has its own setup page with permissions, events and FAQ.