finally!!! thanks!

thank you!!!

We're very excited to announce that we've improved the way notifications from spammy repositories and users are handled, resulting in clearer, more accurate notification counts.

Notifications triggered by spam accounts are now correctly hidden

We’ve updated notification handling so that when a user or repository is flagged as spam, all notifications originating from their activity are reliably hidden, including past mentions from suspicious accounts. Previously, notifications triggered by spammy activity could remain visible and contribute to your unread repository counters, even after hiding or flagging them. This led to confusion and unnecessary clutter in the notification experience.

Now, once an account or repository is marked as spam, notifications they triggered will no longer show up in sidebar counters or counts, even if you were mentioned by them before the spam was detected. As part of this change, close to 6 million spam-related notifications were cleaned up across GitHub to help keep your notifications clear and actionable.

How to give feedback

We'd love to hear your thoughts! Feel free to drop a comment in this post with any questions or feedback. 🚀

Also announced in a blog post 2 days later on Dec 4, 2025.

This is a very thoughtful improvement. Spam notifications affecting unread counts was a real pain point, especially when past mentions stayed visible. Automatically hiding all spam-triggered notifications makes the system far more reliable. Appreciate the effort to keep notifications actionable 👌

thanks

If a PR is opened by a spam account and mentions your account (in a repository you have no association with), then even after that spam notification is removed, any subsequent reply to that PR will still notify you and there is no way to block this. See pateljj04/i4i-GoogleClassroomKolibri#1

Even ignoring the repository will not prevent this.