Make the issues only reply as a thread , not to send it to all channel

[yazansharawi]

Select Topic Area

Question

Select Feature Area

• Issues
• Projects

Body

Hello, whenever i create a new issue in slack using github the issue is created and notify all the channel , what i want is to only reply to the specific message i created the task for , can anyone help ?

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[hrishikesh-kocharekar-dev]

To make GitHub issues only reply as a thread in Slack, you can modify the GitHub Slack app's notification settings to only send replies to the specific channel or message where the issue was created. Here are the steps to do so:

Go to your Slack workspace and click on the GitHub app icon in the left sidebar.
Click on the gear icon next to the repository where you want to modify the notification settings.
Select "Configure notifications" from the drop-down menu.
In the "Issue notifications" section, select "Thread reply" instead of "Channel-wide message" in the drop-down menu.
Click "Save" to save the changes.
By default, when you create a new issue using GitHub in Slack, the issue notification is sent to the channel where the Slack app is installed. When you modify the notification settings as described above, replies to the issue will only be sent as a thread to the specific channel or message where the issue was created.

Note that if you have multiple repositories linked to the GitHub app in Slack, you will need to modify the notification settings for each repository separately.

[yazansharawi]

Hello There, thank you for reaching out, unfortunately I can’t find any gear icon on my slack workspace , can you explain more ? I will be greatful if you can attach any image.

thank you again !!!!

[github-actions[bot]]

🕒 Stale Discussion Alert 🕒

This Discussion has been labeled as stale by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This stale notification will only apply to Discussions with the Question label. To learn more, see our recent stalebot announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[joshflint]

Adding here, that there is no gear or configuration settings that I can find anywhere, so I feel stuck with GitHub spamming my channels

[VincentC4S]

Same issue over here. Notifications settings are nowhere to be found. The Slack integration is posting to the thread as well as the channel and the timeline gets really messy because of this. How can I stop the Slack integration posting to a channel?

[OskarAira]

Same issue here, unable to find the above described settings.

[TeemuSo]

Same issue here. What exactly is the added value of threading, if we can't scope discussions to a single thread?

[theodoretliu]

Also was unable to find the gear icon or settings

Read https://github.com/integrations/slack?tab=readme-ov-file#threading to go the opposite direction, /github subscribe repo comments:"channel" - maybe /github subscribe repo comments will enroll in thread behavior?

Also on same github page, is mentioned /github settings to disable/enable threading on an individual level

[gwerbin-tive]

The only option I see is to "disable threading". But I see no option to disable the "also sent to channel" thing.

[rewazzu]

Same Issue

[wdhowe]

This is still a problem today and makes channels too noisy with updates. Having the configuration available to disable posting to the channel too would be very useful.

[bgalvao]

likewise, facing the same issue, I had to disable threading entirely it was just too noisy.
and it's a slack channel with 3 contributors that I'm talking about.