Replies: 1 comment 3 replies
|
Maybe it could be implemented into threads (when they will get implemented). Basically channel threads could have webhooks. You could also set permission for a thread to only view message history? Kinda channel inside a channel. |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
Project and topic channels often need both conversation and a stable source of information, such as updates from a GitHub webhook
Currently, these updates must either be mixed into the chat, where they can get buried, or placed in a separate channel, which splits the context and clutters the channel list
Proposal
Allow text channels to optionally have a separate read-only information area, such as a tab or side panel
Members could continue chatting normally while bots, webhooks, or permitted roles publish updates to the information area
This could be an optional feature for text channels or a dedicated channel type
Notes
For example, a project channel could contain its regular discussion and a GitHub activity feed without requiring separate #project-chat and #github-feed channels
The exact presentation is flexible
The important part is keeping related information and conversation together without mixing both message streams.
Checks
All reactions