11

I have cleared my GitHub notification inbox, deleted the browser cache and logged out and back in to GitHub. Still it shows me a "1" next to "Inbox" and the blue notification dot. How can I fix this? This happens under Linux with Gnome on both the newest Firefox Developer Edition 124.0b7 and Chromium "Version 122.0.6261.94 (Official Build) Arch Linux (64-bit)".

enter image description here

2
  • Likely a bug on their end. Contact support Commented Mar 11, 2024 at 12:57
  • 1
    @DanielA.White: Thanks, I filed a bug report at <support.github.com/ticket/2665893>. Commented Mar 11, 2024 at 14:11

1 Answer 1

23

The following answer by GitHub support successfully got rid of the blue dot:

The issue you are experiencing is a known bug that often occurs when you receive notifications from accounts that have been suspended or marked as spammy. Our engineering team is aware of this issue, and they are actively working to address it. While I cannot make any specific promises regarding updates or changes, please rest assured that your report is being investigated.

In the meantime, there is a workaround you can try. You can mark all notifications as read using our Activity API. To do so, please run the following command, replacing $TOKEN with your personal access token. Note that the token needs to have notifications scope checked.

curl -X PUT -H "Accept: application/vnd.github.v3+json" -H "Authorization: token $TOKEN" https://api.github.com/notifications

Please note that this workaround will not remove the repository from the list of repositories you have received notifications for, which appears on the left panel of the notifications page. Unfortunately, it is currently not possible to edit that list.

Sign up to request clarification or add additional context in comments.

4 Comments

I got error: { "message": "Resource not accessible by personal access token", "documentation_url": "docs.github.com/rest/activity/…", "status": "403" }
Issue token like this: Settings > Developer settings > Personal access tokens > Tokens (classic) > Generate new token > Generate new token (classic) > enter name, toggle "notifications" scope, click "generate token"
With GH api I prefer ro use their CLI tool like this gh api -X PUT /notifications it is just simpler to use than plain curl. You just need to gh auth login first and then you can interact with API without any personal access tokens.
It seems like a classic PAT might be needed - I cna't find the notification scope on the fine-grained tokens

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.