You'll see you have access to the #development channel
That's it really. The !sunmute command works in the #development channel too.
What roles do you think cause this behavior? The @git-contributer role
What command/action did you do? !smute
Where did you do this? #commands
When did you do this? (helps when tracing logs. use UTC) 8:09 AM, January 28
Expected behavior
A clear and concise description of what you expected to happen.
I would use !smute, and only have access to the #study mute channel, not the #development channel.
Please Include
!version
Below 1.0.4To Reproduce Steps to reproduce the behavior:
!smute
on any channel#development
channel!sunmute
command works in the#development
channel too.@git-contributer
role!smute
#commands
Expected behavior A clear and concise description of what you expected to happen. I would use
!smute
, and only have access to the#study
mute channel, not the#development
channel.