Subscribed, not by my hand, to a snippet that cannot be unsubscribed from.
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
-
As
forum.gitlab.com/t/89184explains:I’m somehow subscribed to
snippets/1895688but didn’t subscribe myself, and only contributed a comment after receiving e-mails. Another person (a respondent to the linked comment) is experiencing the same. -
As
support.gitlab.com/hc/en-us/requests/601831does, too:I expect to see a toggle, like I do at PRs and issues. However, I do not:
Steps to reproduce
The aforestated is all I know.
Example Project
What is the current bug behavior?
Users are subscribed to a snippet, without action on their part, which they cannot unsubscribe from.
What is the expected correct behavior?
They shouldn't be subscribed, and they should definitely be able to unsubscribe.
Relevant logs and/or screenshots
Output of checks
This bug happens on
GitLab.com.
Results of GitLab environment info
Inapplicable.
Results of GitLab application Check
Inapplicable.
Possible fixes
Unknown, for I know not the cause.

