-
Notifications
You must be signed in to change notification settings - Fork 130
Gist comments and mentions don't trigger notifications #21
Comments
This comment has been minimized.
This comment has been minimized.
I asked support about this, and on May 31st they said:
|
👍 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 |
If anyone has any 3rd party solutions to this, then do please post! |
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 |
This comment has been minimized.
This comment has been minimized.
1 similar comment
👍 |
👍 - very annoying |
This comment has been minimized.
This comment has been minimized.
1 similar comment
+1 |
👍 |
@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? |
@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. |
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) :) |
This comment has been minimized.
This comment has been minimized.
1 similar comment
👍 |
This comment has been minimized.
This comment has been minimized.
For the interim, I made a script that send me emails about new comments left on my gists and I made it available at https://github.com/kramerc/gist_notifier. |
This comment has been minimized.
This comment has been minimized.
👍 — it would be great! |
This comment has been minimized.
This comment has been minimized.
1 similar comment
👍 |
This comment has been minimized.
This comment has been minimized.
2 similar comments
👍 |
👍 |
@jookyboi could you perhaps please bring a comments listing and comments notifications into gistbox? |
Oh man. Just discovered an important comment from 5 months ago on one of my gists. Hope they don't think I'm an asshole for not replying. Was never notified :/ Please help us not look like assholes :) |
This comment has been minimized.
This comment has been minimized.
1 similar comment
+1 |
CEO has been made aware https://twitter.com/natfriedman/status/1105868787419496448 |
This is truly a blessed day. |
And there was much rejoicing!
…On Wed, Mar 13, 2019, 11:37 AM Jakob Cosoroabă ***@***.***> wrote:
CEO has been made aware
https://twitter.com/natfriedman/status/1105868787419496448
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACI8OYm75nZ3H5_Qn278wRd8tHi1NLB4ks5vWSkogaJpZM4AtVsL>
.
|
The GitHub App "Always Be Closing" (ABC) now has gist comment notifications. You can use it in the interim until GitHub implements the feature :) https://www.thoughtdealership.com/post/gist-notifications/ |
Hey you all, Let's close this 6-year-old running issue for good ❤️ |
He actually replied !!! - Check it out the tweet |
Pretty much confirms what we already know what would happen it's just a matter of when |
👋notifications for new gists (and new comments on gists) are now available! https://github.blog/changelog/2019-05-08-gist-notifications/ hoping this helps you all out 😊 |
Thank you becca 🎉 |
Big day! 🎉 I'm surprised that I have to manually click Subscribe on each of my gists though, shouldn't I be subscribed automatically? |
@BenMorel we have not yet transitioned authors to being automatically subscribed to their own gists. this is up next 👍 |
@becca @BenMorel but then the help page is misleading? Or is the transition being done in the next few days / hours?
|
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? |
It sounds like it will take some time, there are probably tens of millions of gists to process through |
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. |
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 😁 ) |
@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! |
@becca Amazing work, thank you! 👏 |
@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 received email notification within a few (2-5) minutes of when the comment was made. |
This comment has been minimized.
This comment has been minimized.
I can confirm email notifications are now working. |
👋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/ |
this used to work.
to reproduce:
The text was updated successfully, but these errors were encountered: