I wanted the best GitHub notifications in Slack, so I built it

March 17, 2026
github slack devtools productivity notifications gitnotifier

Two things really annoyed me with GitHub notifications.

First: when I merge my own PR and break CI/CD on main, I am not alerted.

Second: existing notification solutions often spam me with bot comments and status updates (Vercel, Cloudflare, Wiz, CodeRabbit, and more), while human review signal gets buried under these notifications.

That is why I built GitNotifier: GitHub notifications in your Slack DMs.

TL;DR: it alerts you when your PR breaks main, on comments written by human on your PRs, you can mute bots, etc ;) (and more! keep reading eheh)

The blind spot: post-merge CI failures on main

Most GitHub notifications are PR-centric. That sounds fine until you realize what happens after merge.

If your PR gets merged, and then CI/CD fails on main, you often miss it. The branch is red, production might be blocked, and you discover it too late.

I even wrote a workaround years ago using GitHub Actions and Slack webhooks: Sending slack notifications with github actions. It's quite manual because you need to edit your GitHub Actions in all your repos and configure the right tokens... but it did the job for a while.

It still felt like duct tape. I wanted something that works out of the box.

Bots now talk more than humans

On many PRs, I get more bot comments than human comments.

You know the pattern:

  • Vercel preview updates
  • Cloudflare checks
  • Wiz security notes
  • Bito.ai suggestions or CodeRabbit AI review comments
  • and more

None of these are inherently bad. I actually like reading them (sometimes) when I review a PR. The problem is they should not be notifications. Kind of like with a service level objective (SLO): you only want alerts on symptoms, not for every small CPU burst in your VMs.

In 2026, reviewing code often takes longer than writing code (thanks Claude, ChatGPT & co). If the most important part of the workflow is human review, then human comments should have the highest signal.

Here is a graph from the GitNotifier analytics page to show this clearly in the repos I work with: bot comment volume often exceeds human comment volume (crazy, right?).

Bot comments often outnumber human comments in PRs

Existing tools did not really solve it for me

I tried a lot of options. Most had one or more of these issues:

  • Too expensive for what they do
  • Hidden inside enterprise bundles
  • Focused on employee monitoring or performance tracking
  • Poor UX (some honestly felt vibe-coded)
  • Limited customization

I "just" want good GitHub notifications in my DMs, not a full-blown team performance tracking system costing me a house per month. Notifications that are actually useful in daily engineering work.

Most PR reviews involve 2 people, so why spam a channel?

A PR review is usually between:

  1. the author
  2. the reviewer
  3. (a review agent? but they are noisy 😁)

Sometimes 3 people. More than that is rare.

So sending every update to a shared Slack channel is often the wrong default. It creates ambient noise, trains people to mute channels, and increases alert fatigue for everyone. The fewer messages, the better.

IMHO, the right destination for most PR events, such as comments, is personal Slack DMs, not public channels.

Shared channels should stay for shared context. Direct actions should go to directly involved people.

What I wanted instead

I built GitNotifier around a few principles:

  • Signal over volume
  • Human-first notifications
  • Strong customization
  • DM-first delivery
  • Actionable alerts, not passive spam

In other words: fewer notifications and better notifications.

Do things from Slack, do not just get pinged there

Another frustration: every notification forces context switching.

I wanted to stay in Slack and continue working, so GitNotifier lets me do things directly from Slack:

  • react to comments
  • reply to comments
  • merge PRs that are ready

The goal is simple: reduce tab-jumping, keep momentum. As a big fan of Raycast, I want to be more ✨productive✨ when I use a tool.

DX matters: setup should be boring

Dev tools die when setup is painful.

The flow I wanted:

  • Admin installs 2 apps (GitHub and Slack)
  • Users join in 1 click from Slack

That is it.

No heavy rollout project. No setup overhead. No long onboarding docs. Just connect and start receiving useful notifications.

What changed for me

After using GitNotifier daily:

  • I miss fewer critical CI issues
  • I focus faster on human review threads
  • PR handling is faster because actions happen in Slack, and PRs get merged faster.

I did not need more notifications. I needed better ones 😁

If you want to give it a try, check out GitNotifier

Gitnotifier notif in slack

If you are dealing with the same GitHub + Slack notification fatigue, I would love your feedback!

Back to Blog