integrations
Add a checkbox to not post replies to main thread for PR and deployment slack integration messages
Is your feature request related to a problem? Please describe. It's a huge bummer that my team had to unsubscribe from PR and deployment messages because they're just so huge and noisy and post so many updates to the main channel as well.
Describe the solution you'd like There's already a toggle for not using threading, if there could also be a toggle so that when using threading, updates didn't also get posted to the main thread.
Describe alternatives you've considered I've written my own script and workflows so that I can post and update messages to the appropriate channels and keep everything tidy and concise and only post replies in the thread, not as separate messages.
Additional context Add any other context or screenshots about the feature request here. Look at the differences between my deploybot at the top, and then everything else that got spit out. Like, some of that is kinda cool, but also, SOOOO NOISY. Message at the top has all the information for 5 deployments (2 OSs each) and a final status message. It's all one major deployment with a bunch of sub-deployments from our point of view, so having the channel absolutely explode and be a full top to bottom on a 27" monitor just doesn't seem reasonable. I normally have slack in the top third of one of my monitors, so it's got 2160x960 screen real estate, and for conversations, that works entirely fine, but even when I go fullscreen on my primary monitor so it has 3840x2160 to work with, you can see it takes up the whole screen for just one action. It was pretty immediately impossible to find anything in our releases channel when we turned on that integration, so we had to turn it off super quick.
@rmhrazorhead We have recently introduced actions workflow notifications. It will also give you updates about your environment deployments in the form of a thread. And we also added support to filter your actions notifications based on requestor, branch, workflow etc. We recommend customers to move away from existing deployment notifications to new workflows notifications.
+1
I want to give this request a bump. It would be much more usable if all the replies to a particular deployment or PR were grouped only under the thread. Having all the thread replies posted into the thread and into the main channel is too noisy and my team and I are missing important things simply because there is too much stuff in the main channel.
It seems like it would be a fairly simple change to just NOT post in the main channel. I would really love it if we could make that happen!
+1 to this. Our team prefers to have the update posted in the thread when a PR is merged but not to the main channel but I don't see any way to change that setting.
We too would really like this option. I see no reason why the integration should be opinionated on which kind of messages are also posted to the main channel and not let us change it.
We currently have to disable workflow notifications since they are too noisy, but would keep them if they kept all messages in threads instead of also posting some to the main channel.
