I did a brief skim but couldn't find an option...
# configs
j
I did a brief skim but couldn't find an option...
😬 1
p
Is it worth having a separate channel just for GitHub notifications? 'cc @Simon Pearce
j
I don't think so, I think having it hear would nudge people to anybody to check/do the review . Or we put them all on #request-review...
p
I think if it's too noisy then people will just mute the channel
So definitely not #request-review
j
Yeah exactly... That's why I felt it was ok for test-data and conifgs because they are both low traffic
I think a dedicated channel for all will just go the same way as request review in that it'll be too noisy/boring (no other reason to go there other than to 'get more work' so will be muted too 😅)
👍 1
p
True 👍🏻
I guess my worry is that the same will be true with the notifications in this channel, and people asking questions will be lost in the noise.
j
Yeah I see your concern, this was aimed at being an experiment to get around an issue raised by Simon that people get frustrated with having to submit test data because reviews apparently take a long time. To be fair though the channel is also low traffic itself anyway so I'm hoping it won't be too much of an issue. But we will see 👍
s
https://github.com/integrations/slack?tab=readme-ov-file#threading
Only the parent card is posted to the channel and rest of the notifications will be added as a reply in the thread. 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.
j
Meh big assumption there but fair enough
I guess nothing we can do for now
s
Definitely
File an issue? 😉
j
There's been no activity in 3y or something
😬 1