The whole story.
One message.
From opened to merged, the same Slack message stays current. Context stays together. Your channel stays quiet.
Updated, not repeatedGitHubSlackFinally on the same page.
Better reviews.
Less chasing.
Keep pull requests moving, right from Slack.
Clear next steps. Quiet updates. More time to build.
Made for GitHub. At home in Slack.
pull-requests
Less noise. More progress.Today
Give it a try. Move this PR forward.
ONE PULL REQUEST. ONE LIVING MESSAGE.Your workflow, with a little less work.
LESS ADMIN. MORE MOMENTUM.
Great work gets stuck
between “opened” and “merged.”
PullPig keeps the next step clear, so your team can keep moving.
No new dashboard. No more “did you see my PR?”
The whole story.
The right repo.
The right people.
Route repositories to the channels that own them. Connect GitHub accounts to Slack for mentions that reach your team.
A place for every projectYour next move.
Already clear.
See what needs a review, an author update, or a merge. Check your queue or ask for a team digest.
Less checking, more doingSMALL SETUP. EVERYDAY DIFFERENCE.Fits right into
Fits right into
how you work.
You already have the tools.
PullPig connects the dots.
Make room in Slack.
Add PullPig to your workspace and invite it to your team’s channel.
Bring your repositories.
Install the GitHub App and choose the repositories your team wants to follow.
Connect. Then get back to it.
Run one command in your channel. PullPig takes it from here.
/pullpig route owner/repoYour code stays in GitHub.
Your team stays in the loop.
PullPig reads PR activity and brings the useful parts to Slack.
Your reviews and merges stay exactly where they belong.
What does PullPig actually do?
PullPig brings GitHub pull request activity into Slack. It keeps one message current as a PR changes. Your team sees the status, the next action, and the right people to involve.
Will this add more noise to our channels?
PullPig updates the existing PR message instead of creating a new message for each change. Meaningful updates stay in its thread. Draft PRs wait until they are ready for review.
Can we choose which repositories go to each channel?
Yes. Run /pullpig route owner/repo in the destination Slack channel. Use /pullpig routes to see your workspace’s routes. Each repository connects to a channel in that workspace.
Does PullPig change anything in GitHub?
No. PullPig receives GitHub events and can refresh PR snapshots through read-only API calls. Reviews, comments, and merges still happen in GitHub.
Are digests sent automatically?
Run /pullpig digest for an immediate summary. Use /pullpig digest schedule HH:MM for a daily digest. Schedules use UTC and require SQLite storage. Configured route admins control scheduling.
How do we get started?
Connect your Slack workspace, install the GitHub App, and route a repository to a channel. Use the setup guide for a hosted installation or your own PullPig server. Published pricing and billing are not available yet.
YOUR TEAM HAS BETTER THINGS TO DO.
Less “any updates?”
More good work.
Give your pull requests a little forward motion.
Add to Slack A small addition to Slack. A calmer way to ship.