-
BetaWas this translation helpful?Give feedback.
Replies: 14 comments 11 replies
-
see on another device and close ur session btw |
BetaWas this translation helpful?Give feedback.
-
Go to Settings → Notifications Click on your profile picture in the top-right corner and select Settings. In the left sidebar, click on Notifications. Click "Check" or "Sync" to force a synchronization On the Notifications settings page, look for a button that says "Check" or "Sync" near the top. Clicking this will force GitHub to re-sync your notification count with the server, which should clear any ghost notifications. |
BetaWas this translation helpful?Give feedback.
-
or clean ur cookies and try on incognito |
BetaWas this translation helpful?Give feedback.
-
For anyone else facing this, running the following JavaScript snippet in the browser's developer console on the notifications page immediately clears the ghost notification. Just remember to type |
BetaWas this translation helpful?Give feedback.
-
Go to Settings → Notifications Click on your profile picture in the top-right corner and select Settings. In the left sidebar, click on Notifications. Click "Check" or "Sync" to force a synchronization On the Notifications settings page, look for a button that says "Check" or "Sync" near the top. Clicking this will force GitHub to re-sync your notification count with the server, which should clear any ghost notifications. |
BetaWas 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.
-
Also had ghost notifications from these (not existing) repos. The script solution worked. Maybe it was some "spam attack" |
BetaWas this translation helpful?Give feedback.
-
For me it was gitcoini/gitcoincom that had the undeletable notification: |
BetaWas this translation helpful?Give feedback.
-
@github@look Could you have a look and tell the right people? |
BetaWas this translation helpful?Give feedback.
-
Same issue here! |
BetaWas 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.
-
Someone mentioned me in a private repo that I have no access to and I see this problem too. ![]() It started a month or so ago and is now getting quite annoying as it tickles the notification/inbox dot so I permanently have unread messages I am unable to action on. @babelllll has not provided a fix, this needs to be resolved at GitHub's end as it is leaking information about repos I cannot access into my notifications inbox. |
BetaWas this translation helpful?Give feedback.
-
Please refer to this link to eliminate the annoying points. |
BetaWas this translation helpful?Give feedback.
-
Use this direct API call while logged in: https://api.github.com/notifications with a Personal Access Token to mark all as read. |
BetaWas this translation helpful?Give feedback.
-
I had the ghost notification from paradigm repos, and I found this gh api /notifications?all=true --paginate | jq -r '.[] | select(.repository.full_name == "<owner>/<repo>") | .id'|whileread thread_id;do gh api -X DELETE "/notifications/threads/${thread_id}/subscription" gh api -X DELETE "/notifications/threads/${thread_id}"done |
BetaWas 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.
-
👋 I'm excited to share that we just shipped a major improvement to how notifications from spammy repositories and users are handled. They're now correctly hidden so you won't see inaccurate counts anymore. You can check out more details in our changelog (https://github.blog/changelog/2025-12-04-notifications-triggered-by-spam-accounts-are-now-correctly-hidden/). Let me know if you have any other questions or are still experiencing any issues! |
BetaWas this translation helpful?Give feedback.





For anyone else facing this, running the following JavaScript snippet in the browser's developer console on the notifications page immediately clears the ghost notification.
Just remember to type
allow pastingin the console first to enable pasting the code.