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.
Maybe as a configurable (rate-limited) volume- or time-based option? Maybe first 1, 10, 100, &c or every 10 👍s, or a summary of all reactions every week? I can't imagine anyone who'd want an e-mail for every reaction every time.
Reacted by TPS, Glen, Jonathan Hettwer, David Perry, Andréy Lesnikóv, Prasad Katti, Teppo Koivula, Jānis Elmeris, Azar, Kevin Orr and 6 more
I need a way to unsubscribe from e-mail followups to all of my commits. They're invariably low quality complaints. I would prefer not to see any of them in my inbox.
I also need a way to manage every thread that I'm subscribed to. I particularly want to be able to unsubscribe to every closed ticket and issue that I'm currently subscribed to. I'd also like the ability to lock any issue or PR that has been closed for more than a month to force users to open new issues (if they can't be bothered enough to open a new issue, I can guarantee you we can't be bothered to reconsider an old closed one).
I don't even care about the vast majority of the open ticket and issues that I'm currently subscribed to which simply don't have any time to get to them. These days my response to someone pinging an issue with "any updates on this issue?" is just to whack "unsubscribe" and i'd like to automate that so that I don't see it in my inbox the first time.
And this is the reality of working on a project with hundreds and hundreds of open issues (even after having a weekly triage process to try to get some timely responses on them. There are going to be hundreds of legit issues that are going to get lower priorities than other issues and get queue starved -- for the people who hit those issues it sucks to be them, but its completely non-productive and frustrating to get their complaints showing up in e-mail on a daily basis.
Pretty much the only e-mails I want to get are current open issues where I'm actively working on solving them or reviewing or writing code that is getting written. We have a triage process where we block out chunks of time every week to searching through issues and PRs and grooming them. Outside of that, I don't need /anyone/ pinging me. For my own sanity, I just can't care, because there's nothing I can do about it.
Reacted by TPS, Adam Spiers, Azar, Liam DeVoe and Vishesh Handa
I can do that. Somewhere there's an open issue already about getting the list of subscribed to issues through the API. I went through that exercise a few days ago and what I found is that I can ultimately get back the list of subscribed-to-threads from the API, but to 'click the unsubscribe button' programmatically you need to know the 'thread id' which you can only pull off of the notifications page /after/ a notification actually comes through. What the webpage does is an AJAX call to an internal API that requires a web session, and that's where my knowledge of how to fake-out being a browser kind of hit a wall...
On a low-volume repository (such as the private one I share with coworkers) I would like an email notification when someone adds a reaction to a thread. Is this currently possible? I don't see any setting under notifications to control emails when people add reactions.
Oh, I see, that's exactly the issue this is about, and the discussion is about making it off by default (which I'm perfectly fine with).
Reacted by TPS, Grant, Danny Hermes, Oliver Azevedo Barnes, Paulo Diovani Gonçalves, Gianni Ferullo, Marc Fallows, Arthur Visser, Andrej Kazakov, David Chambers and 21 more
I would change the title to an in-site "notification", rather than email.
It should be off by default, and should be configurable so that we can request to be notified only for reactions on first comment (i.e. the main issue), excluding the follow up comments.
Reacted by Shreyas Minocha, warptozero, Jasper van Heugten, PhD, Dalibor Karlović and sienori
I'd still like to see this. I often ask people questions and they respond with thumb-up reactions (indicating for me to proceed), but I don't notice for hours/days until I check the issues again manually.
Reacted by TPS, Fabian Marz, Thomas Landauer, Brandon Tulsi, Frank Steffahn, Mathis Michel, Blake Simmon, Jonah Graham, Dalibor Karlović, Charlie Hund and 2 more
@arderyp I've upvoted your comment to agree, I know you'll not know otherwise. 👼
This comment is meant to highlight one other important issue IMO: the reaction notification goes to the author of the content we're reacting to, but since currently they'll not know about it, you need to mention them and notify everyone in the thread, most of which shouldn't get that notification. Making the reactions dispatch notifications actually makes the conversation more precise.
Activity
TPS commentedon Apr 3, 2016
Maybe as a configurable (rate-limited) volume- or time-based option? Maybe first 1, 10, 100, &c or every 10 👍s, or a summary of all reactions every week? I can't imagine anyone who'd want an e-mail for every reaction every time.
lamont-granquist commentedon Apr 3, 2016
PLEASE make this option OFF by default. Or have some big button I can mash to make it ALL go away like some kind of nightmare that I can wake up from.
I already have to wade through too much github e-mail and there's insufficient ways to manage and control it all.
TPS commentedon Apr 3, 2016
So, @lamont-granquist, https://github.com/settings/emails & https://github.com/settings/notifications don't cover you now?
lamont-granquist commentedon Apr 3, 2016
Not remotely close.
And this is the reality of working on a project with hundreds and hundreds of open issues (even after having a weekly triage process to try to get some timely responses on them. There are going to be hundreds of legit issues that are going to get lower priorities than other issues and get queue starved -- for the people who hit those issues it sucks to be them, but its completely non-productive and frustrating to get their complaints showing up in e-mail on a daily basis.
Pretty much the only e-mails I want to get are current open issues where I'm actively working on solving them or reviewing or writing code that is getting written. We have a triage process where we block out chunks of time every week to searching through issues and PRs and grooming them. Outside of that, I don't need /anyone/ pinging me. For my own sanity, I just can't care, because there's nothing I can do about it.
TPS commentedon Apr 4, 2016
@lamont-granquist I think it'd be quite useful if you create (& then unsubscribe from 😉) an issue for each of the • points & subpoints above.
#229 seems to have some relevance for you, also.
lamont-granquist commentedon Apr 4, 2016
I can do that. Somewhere there's an open issue already about getting the list of subscribed to issues through the API. I went through that exercise a few days ago and what I found is that I can ultimately get back the list of subscribed-to-threads from the API, but to 'click the unsubscribe button' programmatically you need to know the 'thread id' which you can only pull off of the notifications page /after/ a notification actually comes through. What the webpage does is an AJAX call to an internal API that requires a web session, and that's where my knowledge of how to fake-out being a browser kind of hit a wall...
lamont-granquist commentedon Apr 4, 2016
#633 #634 #635 all cut
BBI-YggyKing commentedon Jun 13, 2016
On a low-volume repository (such as the private one I share with coworkers) I would like an email notification when someone adds a reaction to a thread. Is this currently possible? I don't see any setting under notifications to control emails when people add reactions.
Oh, I see, that's exactly the issue this is about, and the discussion is about making it off by default (which I'm perfectly fine with).
marktani commentedon Feb 1, 2017
Any new thoughts about this feature request? This would be tremendously helpful for a few projects
li-boxuan commentedon May 9, 2018
I want to receive notifications for reactions. Is there any third-party tool for that?
weitzhandler commentedon Jul 19, 2018
👍
This is very compelling.
I would change the title to an in-site "notification", rather than email.
It should be off by default, and should be configurable so that we can request to be notified only for reactions on first comment (i.e. the main issue), excluding the follow up comments.
arderyp commentedon Jul 29, 2020
I'd still like to see this. I often ask people questions and they respond with thumb-up reactions (indicating for me to proceed), but I don't notice for hours/days until I check the issues again manually.
dkarlovi commentedon Apr 9, 2021
@arderyp I've upvoted your comment to agree, I know you'll not know otherwise. 👼
This comment is meant to highlight one other important issue IMO: the reaction notification goes to the author of the content we're reacting to, but since currently they'll not know about it, you need to mention them and notify everyone in the thread, most of which shouldn't get that notification. Making the reactions dispatch notifications actually makes the conversation more precise.