💬 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. ⭐

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

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

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

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

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.

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

Exceedingly noisy. Please have them in thread only

still nothing about this?

I really need this too!

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.

Also desired here, far too noisy

👍 it is way to noisy

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

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

I agree with threading, but sending replies to channel is too much, PRs get lost along the way. Please GitHub, make it enjoyable rather than painful.

Adding a vote for this, the option to choose 'noisy' vs 'quiet' would be very, very helpful.

I don't understand why the default would be "Also send to channel". Turning this off it is too noisy.

This would be a great configuration option.

it's absurd how you have a market competitor https://pullnotifier.com/ just because you refuse to fix this

I’m seeing the same issue on our side. The thread updates are useful, but having every update posted directly in the channel can make things quite noisy, especially when there are several PRs being merged. An option to keep these updates in the thread only would make the integration much easier to manage.

Since there is a way to actually make the main thread even noisier, with options like /github subscribe owner/repo comments:"channel" to force comments to get sent to the main channel, could we get the inverse for all event types? Something like /github subscribe owner/repo pulls:"thread" for each event to make the messages stay in the thread only.

I also agree that "thread only" should be the default with the opt-in option to send some or all of the events to the main channel.