Gist comments and mentions don't trigger notifications

[max-mapper]

this used to work.

to reproduce:

• make a gist
• have someone leave a command or @ mention you
• you won't receive any emails

[luk-]

This

[kastiglione]

I asked support about this, and on May 31st they said:

Notifications for gist comments isn't implemented now, but it's something the team has discussed, so this could change in the future. We'll definitely announce this on our blog if it gets pushed out.

[balupton]

👍 it is soooooooo infuriating, it is a common occurrence where I discover a very important comment or even a job offer that is a year old or so on a gist

[balupton]

If anyone has any 3rd party solutions to this, then do please post!

[commonsguy]

And, according to this gist, this is a fairly popular feature request/bug fix. What is the point of having comments if the developer of the gist will not hear them (short of manually monitoring the page)? After all, we cannot use existing tools for change detection, partially because the page always changes ("Created NNN days ago") and partially because robots.txt blocks monitoring of gists.

[swrobel]

👍

[r-a-y]

👍

[eddieajau]

👍 - very annoying

[BrainCrumbz]

+1

[pstadler]

+1

[X4]

👍
I really need it too, but don't immediately send the notification and don't include the message in the notification!
Every edit should increase the notification by 15minutes.

[patcon]

@X4 that sounds like i might be a separate issue request that's great in its own right..? re: delaying notifications using some known criteria.

Would it be cool to open another issue on that?

[X4]

@patcon hmm, I believe that it's not required, because the changes would be both very simple and results in extending the function responsible for writing a notification flag that makes the notification icon on the top left shine. I assume GitHub uses some kind of asynchronous message passing system, so delaying a notification due to an edit under 15min would just require an update of the timestamp in the message queue.
For efficiency reasons, I would not set it to a fixed time of 15minutes, but let it be larger, when required, so that more queued items can be updated at once. This would result in less updates.

[patcon]

Sorry, wasn't saying it wasn't simple, but just that it's not what the OP was asking about, and that it would definitely be useful for other things (as opposed to just gist comments) :)