Code of Conduct
What article on docs.github.com is affected?
When managing notifications, I often need to open each notification to check whether I should respond, save it, or mark it as done.
What part(s) of the article would you like to see updated?
The notification list shows the repository, title, and activity, but users may still need to open the notification to see more details before deciding what to do.
For example, when reviewing multiple issue or pull request notifications, I may want to quickly identify which ones require my attention and which ones I can dismiss.
Suggested improvement:
Add quick actions or more context directly in the notification list, such as:
- A way to mark a notification as done without selecting it first
- A way to save a notification directly from the list
- More visible indicators for unread or recently updated notifications
This would help users manage their inbox faster without opening every notification.
Additional information
I can reproduce this behavior consistently when managing notifications with multiple unread items.
Steps to reproduce:
- Open the GitHub Notifications page.
- Have multiple notifications from issues or pull requests.
- Try to decide which notifications need attention without opening them.
- Notice that additional details are only available after opening each notification.
This occurs whenever I review a list of notifications with multiple updates.
This could affect users who receive many notifications daily, especially users who collaborate on multiple repositories and need to quickly prioritize updates.
Code of Conduct
What article on docs.github.com is affected?
When managing notifications, I often need to open each notification to check whether I should respond, save it, or mark it as done.
What part(s) of the article would you like to see updated?
The notification list shows the repository, title, and activity, but users may still need to open the notification to see more details before deciding what to do.
For example, when reviewing multiple issue or pull request notifications, I may want to quickly identify which ones require my attention and which ones I can dismiss.
Suggested improvement:
Add quick actions or more context directly in the notification list, such as:
This would help users manage their inbox faster without opening every notification.
Additional information
I can reproduce this behavior consistently when managing notifications with multiple unread items.
Steps to reproduce:
This occurs whenever I review a list of notifications with multiple updates.
This could affect users who receive many notifications daily, especially users who collaborate on multiple repositories and need to quickly prioritize updates.