Allow turning off Slack Integration's "Also sent to the channel" features

[alanwubenchsci]

Select Topic Area

Product Feedback

Body

Hi,

For features where the state changes of a pull request (ready for review, merged) also get sent to the channel (instead of only in the thread), I'd love to have them NOT sent in the channel. Is this possible?

According to the doc, looks like it's set to be sent to the channel by default.

However, the state change activities like close/reopen issue are added to the
thread as reply and also posted to the channel as this might be of
interest to the group.

Thanks in advance,
Alan

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[CalvineHicks]

seconding this discussion. would love to see something updated for this.

[hughobrien]

This is exceedingly noisy for any team using GitOps, please do not post thread updates to the channel by default.

[matthewtusker]

Same here. Our weekly Dependabot automerges tend to blast our PRs channel, along with all the other work we're doing.

[afrazkhan]

Any progress on turning off this interesting choice of default behaviour?

[adamlith]

Installed the app for our organization today. The first thing we thought of was that this was excessively noisy. Please NEVER send threaded updates to the channel. Or at least make it an optional behavior.

[oleh-kolinko]

That's only problem that is stopping us from adopting slack and GitHub integration, it is too noisy

[mikkilevon]

Exceedingly noisy. Please have them in thread only

[marioalvial]

still nothing about this?

[cskevint]

I really need this too!

[prashantchoudhary]

Seriously, we have abandoned two channels so far. As it sends the notifications to the channel, there are multiple entries per PR. This makes the channel unusable for other purposes. And if we create a notificaiton only channel, no one will look into it. Extremely annoying. Ultimate option is to not use this feature and getting back to manually posting the links.

[jamespilcher]

Also desired here, far too noisy

[MartinL83]

👍 it is way to noisy

[Arinbjarnar]

Please make this optional, I'm being asked to remove the integration because of the noise.

[tiagocatulo]

Still nothing on this? I would really like for this to be fixed