Skip to content

One PR · One message

One PR.
One message.

Low-noise pull request notifications for Slack. As a PR moves — reviewed, approved, merged — its one message updates in place. No scroll, no spam.

Get started → See it in Slack

1 · OPENED
🚀 @John Doe, please review PR #169
Start review
2 · IN REVIEW
🚀 @John Doe, please review PR #169
mptooling/notifycat · opened Today at 8:30 PM
👁️ @John Doe reviewing · since 8:41 PM
Start review
3 · MERGED
[Merged] PR #169
reviewed by @John Doe
reviewed by @CodeOwner
✅ 2💬🔀
the same message, updating in place

Your channel becomes a status board, not an event log. Anyone can see where every PR stands at a glance, without scrolling through five notifications to work out whether something still needs eyes.

Why teams run it

  • Quiet

    State changes become message updates and emoji reactions, not new posts. Dependabot bumps collapse to a single compact line. A busy repository produces one Slack line per PR — total.

  • Nothing slips through

    A morning digest resurfaces open PRs that nobody touched yesterday. The "Start review" button shows who is already reviewing. See What you see in Slack for the full tour.

  • Easy to own

    One Go binary, one declarative config.yaml, one SQLite file. The whole configuration is validated against Slack and your git host before boot. Two secrets, no GitHub App, no OAuth.

The problem it solves

The usual way to connect pull requests to Slack is the official GitHub app: /github subscribe owner/repo plus pulls, reviews, and comments. It works, but every event becomes another Slack item. The events are all there; the current state is nowhere.

Notifycat inverts that. Your git host sends PR webhooks, Notifycat routes each repository to the right channel, and one PR keeps one message. Reviews and comments land on it as reactions; merge strikes it through.

Event log official GitHub app PR opened Review added Comment added PR merged message 1 message 2 message 3 message 4 Status board Notifycat opened reviewed commented merged one Slack message

Git Provider Support

Feature GitHub Bitbucket
Webhook signature verification (HMAC-SHA256) Yes Yes
Per-path / monorepo routing Yes (needs GITHUB_TOKEN) Yes (needs BITBUCKET_TOKEN)
Stuck-PR digest Yes Yes
Reactions & review flow Yes Yes
Token auth Fine-grained PAT (Bearer) Access token (Bearer) or scoped Atlassian API token (Basic)

Where next