You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
Gist comments and mentions don't trigger notifications #21
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.
Reacted by TPS, Zachary Yaro, Milán Nagy, Isaiah Odhner, Joff Tiquez, Олег Петрачев, Gibran Malheiros, Zachary Abresch, ROTGP, Harrison Smith and 3 more
👍 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
Reacted by Harris Rasheed, TPS, Jean-Christophe Beaupré, Tyrone Hinderson, Milán Nagy, igops, Joff Tiquez, Rafael Soares Padilha, Erick Navarro, Carlos García-Saura and 6 more
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.
Reacted by TPS, Milán Nagy, ROTGP, Harrison Smith, Will, Dan Lenski and Daniel Shuy
👍
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 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.
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) :)
From now on, you already get automatically subscribed to new gists you create, go ahead and try. The team will make the retroactive transition soon enough.
@BenMorel right now it's only new gists. we're going to work on the backfill to make it easier to be subscribed to gists you have authored from the past. i'll let you know when this lands but as @Scrxtchy mentioned it's a bit of a transition 😅 ...either way, we're on it!
Reacted by Will, Gary Ewan Park, yakov116, TPS and Daniel Shuy
Reacted by Oliver, Benjamin Morel, ChesuCR, yakov116 and TPS
@becca and the entire GitHub team: Thank you very much for implementing this long needed feature! 👍
I can confirm that Gist notifications are now working, provided that you first subscribe to your own Gist.
I understand that eventually GitHub will auto-subscribe the owner to all of his/her Gists, but for now you much manually subscribe to those Gists for which you want to receive notifications.
I received email notification within a few (2-5) minutes of when the comment was made.
Activity
luk- commentedon Jun 5, 2013
kastiglione commentedon Jul 3, 2013
I asked support about this, and on May 31st they said:
balupton commentedon Sep 20, 2013
👍 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 commentedon Sep 20, 2013
If anyone has any 3rd party solutions to this, then do please post!
commonsguy commentedon Oct 2, 2013
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.txtblocks monitoring of gists.swrobel commentedon Oct 11, 2013
r-a-y commentedon Oct 20, 2013
👍
eddieajau commentedon Oct 21, 2013
👍 - very annoying
BrainCrumbz commentedon Oct 30, 2013
pstadler commentedon Oct 31, 2013
+1
X4 commentedon Nov 5, 2013
👍
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 commentedon Nov 5, 2013
@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 commentedon Nov 6, 2013
@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 commentedon Nov 6, 2013
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) :)
mehulkar commentedon Nov 19, 2013
346 remaining items
BenMorel commentedon May 8, 2019
Thank you Becca, will this be retroactive, i.e. will I get subscribed to all of my existing gists soon, or only to my new gists?
Scrxtchy commentedon May 8, 2019
It sounds like it will take some time, there are probably tens of millions of gists to process through
Logerfo commentedon May 8, 2019
From now on, you already get automatically subscribed to new gists you create, go ahead and try. The team will make the retroactive transition soon enough.
BenMorel commentedon May 8, 2019
Indeed, I'm automatically subscribed to new gists. I'll wait a bit before looping through my gists and clicking Subscribe on each of them, then 👍
(or before I finish writing this comment, someone in this thread will have written a script to do this automatically 😁 )
becca commentedon May 8, 2019
@oliveratgithub we'll update the product documentation 👍
@BenMorel right now it's only new gists. we're going to work on the backfill to make it easier to be subscribed to gists you have authored from the past. i'll let you know when this lands but as @Scrxtchy mentioned it's a bit of a transition 😅 ...either way, we're on it!
BigglesZX commentedon May 8, 2019
@becca Amazing work, thank you! 👏
dandv commentedon May 8, 2019
One giant step for Gist! But wait, this hasn't happened yet but will happen 4 hours from now!?
(my time has been set correctly for months, I haven't moved, not using a VPN etc.)
usmonster commentedon May 8, 2019
@dandv wrote:
#1576
JMichaelTX commentedon May 8, 2019
@becca and the entire GitHub team: Thank you very much for implementing this long needed feature! 👍
I can confirm that Gist notifications are now working, provided that you first subscribe to your own Gist.
I understand that eventually GitHub will auto-subscribe the owner to all of his/her Gists, but for now you much manually subscribe to those Gists for which you want to receive notifications.
I received email notification within a few (2-5) minutes of when the comment was made.
JMichaelTX commentedon May 8, 2019
JMichaelTX commentedon May 8, 2019
I can confirm email notifications are now working.
becca commentedon Jun 3, 2019
👋just a quick update that we have been working on subscribing authors to their own previously authored gists (so you don't have to find and manually subscribe to each). this transition is now done! https://github.blog/changelog/2019-06-03-authors-subscribed-to-gists/