4 ms·

My reading of this is that the only reason OP can't unsubscribe in bulk is because there's currently a bug that affects the two repositories in question. Yeah,

My reading of this is that the only reason OP can't unsubscribe in bulk is because there's currently a bug that affects the two repositories in question. Yeah, that sucks, and I'm not surprised the customer support agent can't do a bulk unsubscribe either; sharing the same API is normally a good thing. I'm not sure expecting a 13 day turnaround on a bug is that reasonable. Can't OP just set up an email filter to handle this for a few weeks until it's fixed?

ddevault 6y ago
If they said they'd work on it, and asked me to wait patiently, then yes, I would definitely do that. Instead, they mischaracterized the problem, offered wrong advice and conclusions, and ultimately they gave this: > We have forwarded your ticket to the Product team who reads and evaluates all feedback, however we cannot guarantee a response to every submission. Are they working on it? Who knows. Will they maintain the line of communication? Probably not. Will I still get these emails for some unknown amount of time? Yes.
- Dayshine 6y ago
  That's a fairly routine response for consumer support, unless you have a big expensive support contract I'm not sure why you would expect more than "We're tracking it, thanks for the report". As to your problem: Why not mute the repositories and use a custom filter on your GitHub notification inbox which you can review every few days to see direct mentions in those repos only?
  - ddevault 6y ago
    I think it's reasonable to expect a better response. This is a matter of their system behaving incorrectly - not of, say, some conspicuously absent feature which I would like to have. It is their responsibility to ensure that their email is not sending unwanted spam to someone else. As the founder of a company which deals with similar problems, I find it entirely reasonable to impose upon myself a responsibility to expediently address problems my software creates for others, and to maintain a clear line of communication with the affected party while the issue is addressed. If GitHub doesn't want to do that, then fine, that's their perogative, but I think their reputation deserves a hit for making that choice. As for the problem itself, I'm sure I can think up any number of workarounds, and I'm likely to apply one at some point. But that doesn't change the fact that I should not have to.

ddevault 6y ago

If they said they'd work on it, and asked me to wait patiently, then yes, I would definitely do that. Instead, they mischaracterized the problem, offered wrong advice and conclusions, and ultimately they gave this: > We have forwarded your ticket to the Product team who reads and evaluates all feedback, however we cannot guarantee a response to every submission. Are they working on it? Who knows. Will they maintain the line of communication? Probably not. Will I still get these emails for some unknown amount of time? Yes.

Dayshine 6y ago
That's a fairly routine response for consumer support, unless you have a big expensive support contract I'm not sure why you would expect more than "We're tracking it, thanks for the report". As to your problem: Why not mute the repositories and use a custom filter on your GitHub notification inbox which you can review every few days to see direct mentions in those repos only?
- ddevault 6y ago
  I think it's reasonable to expect a better response. This is a matter of their system behaving incorrectly - not of, say, some conspicuously absent feature which I would like to have. It is their responsibility to ensure that their email is not sending unwanted spam to someone else. As the founder of a company which deals with similar problems, I find it entirely reasonable to impose upon myself a responsibility to expediently address problems my software creates for others, and to maintain a clear line of communication with the affected party while the issue is addressed. If GitHub doesn't want to do that, then fine, that's their perogative, but I think their reputation deserves a hit for making that choice. As for the problem itself, I'm sure I can think up any number of workarounds, and I'm likely to apply one at some point. But that doesn't change the fact that I should not have to.