|
我开 ticket 收到了回复：
Hi there,
（省略套话）
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.
（省略套话）
Thanks,
xxx
GitHub Support |
