Closed jaspermayone closed 8 months ago
Something like adding a maintainer wouln't work because the bot also sends the requests (just in a different channel)
This issue might be too specific to one project though.
this lgtm
This just came up for welcome committee -- tasks should only be created for posts by the @/toriel bot instead of regular messages.
Context: I posted a message in their channel and it issued a ticket for a welcomer here: https://hackclub.slack.com/archives/GLFAEL1SL/p1707689487371669?thread_ts=1707673191.491869&channel=GLFAEL1SL&message_ts=1707689487.371669
(Happy to break this into a separate issue if you want)
This just came up for welcome committee -- tasks should only be created for posts by the @/toriel bot instead of regular messages.
Context: I posted a message in their channel and it issued a ticket for a welcomer here: https://hackclub.slack.com/archives/GLFAEL1SL/p1707689487371669?thread_ts=1707673191.491869&channel=GLFAEL1SL&message_ts=1707689487.371669
(Happy to break this into a separate issue if you want)
Let's just make sure we are careful not to break the use cases re: slack channel moderation. I kinda interpret Jasper's (this) issue here as "allow for blacklisting specific users in a channel". TBH, the channels that slacker is configured to listen on for these kinds of moderation use cases should not be spoken in by humans period, though... it's also true that messages from the maintainers of a project don't cause new AIs...
closing for now. out of scope for slacker. messages from the maintainers of a project don't cause new AIs.
Would love to be able to specify users / channels or some combo of both to remidy things like this.