Slack: Support subscribing to all features at once

[ocean90]

As someone who wants to have all events pushed to a channel I currently have to do:

/github subscribe owner/repo
/github subscribe owner/repo comments
/github subscribe owner/repo commits:all
/github subscribe owner/repo branches
/github subscribe owner/repo comments

Having an alias like /github subscribe owner/repo all for this would be handy. Another idea would be to support a list of features like /github subscribe owner/repo comments commits:all ....

Related: #291

[kzap]

@bleepers when will this be released or how do we know when there are new features?

[bkeepers]

@kzap This issue will get closed when the feature has been implemented.

[returnlytom]

Ideally, a wildcard would work for both repos within an org, as well as features within a repo. For example:
/github subscribe owner/* *

This would subscribe to all repos in owner/ and enable all notifications.

[hcharley]

For copy pasters looking for a quick command to do this:

/github subscribe owner/repo issues pulls deployments statuses public commits commits:all releases comments branches reviews

[stale[bot]]

Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.

[dentarg]

Absolutely

[webdevbrian]

Bookmarked @charlex response

[setpixel]

Would love to +1 this for a bump :D

[misthioseagle]

issues pulls deployments statuses public commits commits:all releases comments branches reviews

Almost the 50th time I am coming here. I should bookmark this :laughing:

[dennissivia]

I am currently working on this issue and I was wondering about the expected behaviour for the following case:

1. A user subscribes to all
2. A user unsubscribes from a specific topic like comments or so.

Should this be allowed or ignored or be an error? What do you think?

/cc @gimenete @wilhelmklopp

[wilhelmklopp]

@scepticulous that's a really good question.

Since this "subscribing to all" feature caters to the firehose/"I want all possibly activity" use case, I would definitely classify wanting to unsubscribe from specific features _after_ you're subscribed to all as a secondary, less commonly needed use case (though I may be wrong about this).

And with that in mind I think I would just do whatever keeps the implementation simplest for now.

If we do go down the route of not allowing this (perfectly acceptable imho) it might be nice to show a message to the user that helps them understand _how_ they would be able to accomplish the task (i.e. unsubscribe all, and then subscribe the individual types they care about)

[ntwb]

@scepticulous Having just found this issue whilst thinking I'd like to be able to subscribe to *.*, if having done so, to then find out that notifications are far too noisy due to the volume of the _comments_ on a repo then following up with /github unsubscribe owner/repo comments would be the logical step to remedy that scenario

[mariusnita]

I would add that a wildcard subscribe like /github subscribe owner/* * as suggested by @returnlytom should subscribe to all current and future repos, not just the current ones.

[stale[bot]]

Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.

[dentarg]

Absolutely

[redixhumayun]

Is there any movement on this feature? This would honestly be great to have. I keep coming back to this thread to copy @charlex 's command

[LTSCommerce]

I found the copy/paste one liner above didn't work and had to trim this down to

/github subscribe owner/repo issues pulls commits commits:all releases comments branches reviews

[danb235]

Updated copy/pasta since commits no longer uses all due to being a reserved keyword.

Note: Previously we you might have used commits:all to represent all branches. 'all' is no longer a reserved keyword. Going forward, you need to use '*' to represent all branches. If you have already configured with 'commits:all' previosly, dont worry, it will continue to work until you update the commits configuration.

/github subscribe owner/repo issues pulls commits commits:* releases comments branches reviews