GitHub 官方已经在处理了。

GitHub Support (GitHub Support)
Sep 26, 2025, 2:13 AM UTC

Hi ***,

Thank you for bringing this bug to our attention. Our engineers are investigating the issue, and we appreciate your report. While we can't guarantee any specific changes or updates, please know that your report is in good hands and being investigated thoroughly.

Regarding the phantom notification, we apologize for any confusion or frustration this may have caused. One possible explanation is that a user account that mentioned you in a thread has been flagged for potentially violating our Terms of Service. When this happens, the content is hidden from view, including the notification, to protect the privacy of the user account and prevent further violations.

As a workaround, if you're familiar with the GitHub CLI, you can use the script below to mark all of your notifications as read. This may take care of the phantom message, but please note that the 1-0 of 1 message may still persist after the curl command is run. Our engineers are investigating this bug as well.

Running the script to mark notifications as "read" is generally considered safe, as it does not remove the notification itself, only updates the status of the notification. Here is the script:

gh api \
--method PUT \
-H "Accept: application/vnd.github+json" \
/notifications \
-F read=true

If you have a Personal Access Token (PAT), you can also use the following curl command to mark all of your notifications as read. Please note that in order to use the curl command, you will need to replace $TOKEN with your own PAT, which you can create here. Also note that the PAT must have the notifications scope.

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

For your reference, here is the documentation for the Notifications REST API endpoint.

In saying that, I fully understand that you may prefer to wait for a bug fix. Please note that the fix for this issue is complex, and I cannot guarantee a timeline for its implementation.

I hope this is helpful. Please do not hesitate to contact us if you have any further questions.

Cheers,
Nix
GitHub Support

Note: This ticket will automatically close after 3 days of inactivity, but it can always be reopened with a reply or follow-up.