Replies: 4 comments
-
|
This is a welcome improvement, especially considering the effort required to clear spam notifications up to this point (example thread). Thank you for keeping our notifications relevant and free of unwanted clutter! |
Beta Was this translation helpful? Give feedback.
-
|
finally!!! thanks! |
Beta Was this translation helpful? Give feedback.
-
|
thank you!!! |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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. 🚀
Beta Was this translation helpful? Give feedback.
All reactions