Filter out commits from notifications #10525
Replies: 2 comments 1 reply
-
|
This issue is made more frustrating by the existence of such a filter but only for email notifications: Even more so due to the complete inability of the notifications system to provide anything useful in case of force pushes: in that case it just links to an empty diff view, which it almost certainly knows is an empty diff view beforehand. This makes such notifications literally nothing but spam in a project heavily relying on force-pushing PRs. And really feels like being mocked by Github, because in the discussions tab, there is an invisible (unstyled) link to the actual diff for the force push itself (not that I think it should be linked to directly as it is probably expensive, and not at all informative if e.g. the force push was done in order to rebase the PR). |
Beta Was this translation helpful? Give feedback.
-
|
As an addendum to the previous comment, I also want to add that not only are "commit" notifications not the most useful in general, they're utterly useless when the PR workflow is based on rewrite / in-place edition, because in that case github literally shows an empty page which says:
(previously reported at #5373) |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
At the moment, whenever new commits are pushed to a PR, a new notification is sent out to people subscribed to the PR. This can lead to a lot of noise in a user's notifications. Additionally, notifications are also sent out when CI tools push new code (in our case StyleCI). Also see this feedback. I believe, in most situations, notifying users of new commits isn't very useful. GitHub has specific tooling to draw a user's attention to review code: review requests, mentions, comments. Informing users of every new commit is, in my humble opinion, overkill.
I'm a real power user of notifications and use them every single day to keep track of my work at Laravel. I've yet to encounter a situation where I wanted to be informed of new commits being pushed to a PR. This is extremely disruptive for my daily work I must say as I tend to click these notifications and then only see it's a new commit being pushed without a review being requested.
Another annoying thing about this is that the last notification for a new PR is a direct link to the last commit pushed rather than the PR itself. Take the following example:
This was a new PR that reached my inbox (here's the direct link of the notification). When I click it I'm taken to:
Which doesn't really say anything to me. It's just the last commit made by the author to fix a styling issue. I believe the link of a notification for a new PR should always direct to the PR conversation.
To solve this, there's a few actions that can be taken:
I'd be happy to see 1. happen but I can also really appreciate 2. so there's still an option for people who want the current behaviour. I'd appreciate 3. as well but I'd very much look against disabling commit notifications on every single repository I'm watching... Although if really need be, I could live with it.
Two and three can be implemented as a new "Commits" toggle here:
Like I said, I'd very much want to see it disabled by default.
Of course, directly linking notifications to comments on specific parts of code can still be useful. But linking to specific commits is, like I said before, never really useful imho.
I believe that this change will greatly help me be more productive in managing my notifications and daily work. Thanks for your consideration ❤️
Beta Was this translation helpful? Give feedback.
All reactions