GitHub in Slack is noise. Put it back where it belongs.
If your team wires GitHub into Slack, you already know the problem: every push, every CI run, every bot comment lands in the same channel as the message your teammate tagged you in. Real review requests drown in automated chatter — and muting the channel means missing the one mention that mattered.
Why Slack is the wrong inbox for code
- Mixed contexts. Code events sit next to human conversation, so neither gets the attention it needs.
- No triage model. Slack has read/unread, not "waiting on my review". You can't see what's actually yours.
- Loud by default. The fix most teams reach for — mute the channel — throws away the signal along with the noise.
The better split
Keep Slack for humans. Move machine-generated GitHub activity to a dedicated surface where unread counts mean something:
- In GitHub, unsubscribe from notification emails for repos where you only watch CI.
- Install DevNotify and paste a personal access token (which scopes?). Your unread count lives in the macOS menu bar.
- Leave a single Slack channel for release announcements only — everything else stays out.
What changes day to day
You stop alt-tabbing between apps to check whether a PR came back. A number appears in your menu bar when something needs you; it disappears when you've handled it. Review requests get answered faster because they're never buried under a deploy log.
Works with GitHub and GitLab, 100% local — your token never leaves your Mac. $19 one-time license after the trial.