Pullbell / Reduce GitHub notification noise
How to reduce GitHub notification noise
When every notification looks urgent, none of them are. This guide covers the settings that remove most of the noise, and how Pullbell sorts what is left into "needs you" and "FYI".
macOS 13 or newer, Apple silicon and Intel. Source on GitHub.
Find out what is actually noisy
For most developers the noise comes from four places: repos you watch but do not work in, bot comments, CI run notifications, and long threads you commented on once. Fix those before you reach for a tool.
On GitHub: watch less, mute more
- Review the repos you watch in your GitHub notification settings and unwatch the ones you only needed for a week.
- Unsubscribe from a thread you no longer care about from the notification itself, and mute a noisy repo.
- Choose where each kind of notification goes (web, email, mobile) instead of leaving everything on email.
With Pullbell: needs you or FYI
Pullbell sorts each event into one of two buckets. Needs you raises a banner and counts towards the first number in the menu bar (3+5 means three need you, five are FYI). FYI is listed but silent. Defaults:
- Needs you: review requests, comments, replies and mentions from people, approvals, changes requested, ready to merge, conflicts, failed deploys and the optional digest.
- FYI: anything from a bot (an account ending in
[bot]or of type Bot) and every other notification reason.
In Settings, then Alerts, each kind has a switch. Turning a kind off does not delete it: it moves to FYI, so you can still find it in the queue.
Ignore CI run notifications
GitHub can send one notification per workflow run you triggered (reason ci_activity). Pullbell ignores these by default: they are left unread on GitHub and kept out of its list. Failures that matter still reach you as failed-deploy banners and the CI marker in My open PRs. To see them anyway, set CI run notifications to FYI.
Stop duplicates and your own echoes
Your own comments, reviews and pushes never ring, and a burst of comments on one PR is a single banner. If an item gets a newer event from the same thread, it updates in place and moves to the top instead of adding a duplicate row.
Watch only your teams' repos
If you belong to a large organization, you do not need to hear about every repository. In Settings, then Repos, choose to watch only the repos of the GitHub teams you pick, plus any extra repos you type as owner/name. Muted repos always win over the allowlist.
Clear the list in one go
The menu has Clear all with the split shown, such as Clear all (3 + 12 FYI). Marking items done also marks the GitHub notifications read, so github.com/notifications stays clean too.
Ready to try it? Get Pullbell from the latest release, and see GitHub notifications in the Mac menu bar or the pull request notifier for the rest.
Frequently asked questions
How do I stop GitHub CI notifications?
In Pullbell, per-run CI notifications are ignored by default. On GitHub itself, adjust your notification settings for Actions and the repos you watch.
Does turning off a notification kind delete it?
No. In Pullbell a kind that you turn off becomes FYI: it is still listed, but with no banner.
Are bot comments treated differently?
Yes. Anything from a bot account is FYI by default, with no banner.
Can I limit Pullbell to some repos?
Yes. Choose everything, or only the repos of GitHub teams you pick plus extra repos you type. Muted repos are always ignored.
macOS 13 or newer, Apple silicon and Intel. Source on GitHub.