Subscribing to a single feature results in subscribing to all features

[dougwaldron]

Using the command subscribe owner/repo [feature] should only subscribe to that one feature. Instead, it subscribes to all features, and works no differently from subscribe owner/repo.

Even the screenshot from the documentation for this command shows this bug in action:

The unsubscribe command works as expected, so it is possible to subscribe to all features, then one-by-one unsubscribe from the unwanted ones.

[dmeatte-aq]

This is a frustrating issue for us. I can recreate the same issue and workaround as @dougwaldron.

[ortonomy]

ha! this integration is next to useless. Also seeing same issue

using command subscribe ThriveDrive/thrive-drive-frontend subscribe commits "develop"

and response from bot is:

ome of the features enabled for this subscription (discussions) need permissions. You need to update the app before you create/modify your subscription.

errr, I don't have discussions in my repository, and I just tried to subscribe to commits only. What a waste of time

[roechi]

Any news on this? It would be nice to subscribe to only the given feature instead of having to unsubscribe one by one until you got only the one you wanted left.

[brad-dawson]

Our team is also experiencing this issue. As a work around right now we also subscribe to the repo, and then unsubscribe from all of the unwanted features, but this is an extra step that should not be required.

Thanks!

[edecker-elastics]

This is not the answer I hoped for. Five commands to create a notification only for reviews is a really bad UX design. User is far more likely to want to subscribe to one of these features than all.

[4wk-]

This is really annoying! This bug even contradict the documentation... I wanted to subscribe to WORKFLOWS only 👎

[OliverLeighC]

Any update on this?

[Jeyob]

+1 (this seems like a pretty fundamental thing)

[roechi]

I agree.