How to reduce GitHub Slack notification noise
GitHub's default Slack integration fires a message for every push, review, comment, and CI run on every PR. For a team with 20+ weekly PRs, that's hundreds of messages clogging a channel. The fix is switching to a digest model: one scheduled message with filtered, review-ready PRs.
Why does the GitHub bot send so many Slack messages?
Because it forwards every repository event as its own message. Push, PR open, PR close, review submitted, comment added, CI status change: each one is a separate Slack notification. Active teams get buried fast.
What's a PR digest?
Instead of individual notifications, you get one scheduled message that rounds up all PR activity. Drafts, WIP, and already-reviewed PRs get filtered out. Only actionable items show up. HotBot lets you set the schedule (daily, twice-daily, or custom).
Can I filter GitHub notifications by label or author?
With HotBot, yes. You can exclude PRs by label (like 'wip' or 'draft'), by author (bots, specific people), by file path, and by review status. The point is to surface only the stuff someone actually needs to look at.
How do I stop GitHub from spamming my team's Slack channel?
First, remove or mute the official GitHub Slack integration in that channel. Then install HotBot from the GitHub Marketplace, connect your repos, pick the channel, configure your filters, and set a digest schedule. Most people are done in under 5 minutes.
What should I measure to know if it's working?
Look at messages per channel per week, average time-to-first-review, how many PRs sit open for more than a week, and whether your team actually reads the notifications. HotBot's PR status board tracks these. After switching to a digest model, most teams see message counts drop significantly.