Notifications bell indicator stays lit after reading the last unread notification

[palmoni5]

Select Topic Area

Bug

Body

When I have exactly one unread notification and I open it by clicking through to the page it points to, the unread indicator on the notifications bell in the global header stays lit. The notification itself is correctly marked as read on the notifications page, but the header indicator does not refresh to reflect that until I reload the page or navigate again.

The confusing part is that the indicator is not distinguishable from a genuinely new notification. After reading my only notification I still see the dot, so I assume another notification arrived in the meantime, go back to the inbox, and find nothing new. With a single unread item this happens every time, because the indicator should go from "on" to "off" and instead it just never turns off.

Steps to reproduce

1. Get into a state where you have exactly one unread notification (https://github.com/notifications shows one unread item).
2. From any page, confirm the bell icon in the header shows the unread indicator.
3. Click the notification and follow it to the issue / PR / discussion it links to.
4. Look at the bell icon in the header on that destination page.

Expected behavior

Once the last unread notification has been read, the header indicator clears without a full page reload, the same way the notification's own read state updates.

Actual behavior

The header still shows the unread indicator. It only clears after a manual page reload.

Environment

• github.com web UI
• Reproduced on a desktop browser, logged in as a normal user

I could not find an existing report for this; apologies if it duplicates something I missed.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.