Bug: ghost notifications

[callng]

Select Topic Area

Bug

Body

My account was mentioned, but this repository has been deleted or hidden. I can't mark the notification as read because it doesn't even show up. I suspect it was a malicious repository, and now it's hidden or deleted!

This is a ghost notification. How should I mark it as read? Please fix it!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[callng]

https://docs.github.com/en/rest/activity/notifications?apiVersion=2022-11-28#mark-notifications-as-read

[yougotwill]

This did not work for me https://github.com/orgs/community/discussions/174441#discussioncomment-14534860

[callng]

This did not work for me https://github.com/orgs/community/discussions/174441#discussioncomment-14534860

Let the github team fix it instead of using the REST API. 😮‍💨

[simon-ami]

Tanks, that solved it for me:

gh api -X PUT /notifications

[hitrust]

gh api can only mark them as read, so they are still in your inbox as read and in your sidebar repos list.

They should be marked as done.

[xyproto]

I have the same issue.

I have a blue dot in the upper right:

When I click it, I hae this on the left hand side:

But no matter what I do, I can not clear the notifications. When filtering on is:unread the list is empty, but says that it is showing 1-0 of 2.

[callng]

Please refer to https://github.com/orgs/community/discussions/174441#discussioncomment-14482852.
The GitHub team should fix it!

[deniz-blue]

same issue

[KhogaEslam]

I have the same issue. After a mysterious account mentioned my name in an issue, and the account was deleted before reading the notification, now it is a ghost notification

[ngdangtu-vn]

Mine too:

This problem should be fixed by a button on UI because the rest api solution is not a great way. Keeping a script on computer is fine but absolutely not on phone/tablet. And letting this sit there long enough will make me totally ignore a real notifications

[yougotwill]

Using gh api from the suggested answer doesn't work for me. I also listed the notifications via the api and it returns an empty array. But as you can see I still have unread notifications. GitHub can we please get this fixed? 🙏

[yougotwill]

It seems GitHub fixed the issue for me behind the scenes. The notifications above have been cleared

[VioletsOleander]

Same issue here. This is very annoying. :(

[renanfilipe]

same issue here :/

[KhogaEslam]

The issue in the inbox is now resolved [after calling the mark as read API]
But when selecting the flagged repo from the left side, it still exists

[cduguet]

Also having the same type of ghost notifications. If the best way is to let the github team handle it, I'm going to post my case here too.

[DiplomaticRobot]

same here, please fix it! it really annoying!

[Miezhiko]

same issue for me

[nalladev]

Why is this still not fixed.

[lamualfa]

Calling this solved my problems:

gh api \
  --method PUT \
  -H "Accept: application/vnd.github+json" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  /notifications \
   -f 'last_read_at=2022-06-10T00:00:00Z' -F "read=true"

Make sure to install gh cli first and then login using your github account.

[walking-octopus]

javascript:(function(){var f=document.querySelector('.js-notifications-mark-all-actions form[action="/notifications/beta/mark"]');if(f){fetch(f.action,{method:f.method,body:new FormData(f),credentials:"include"}).then(r=>{if(r.ok)setTimeout(()=>location.reload(),500);});}})();