You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really love that you have a Slack plugin, but right now it's not super useful outside of saying that "something was updated in x space". For example:
GitBook [App]
Content of Example Space Name has been updated
This isn't very useful information. We want to keep our wider team informed of changes to our Gitbook docs - even if they don't have a seat on Gitbook. Right now this is a very manual process, because I have to go and summarise the changes each time we push a change.
Instead, it would be lovely if the Slack integration posted a message like:
GitBook [App]
Content of Example Space Name has been updated by Firstname Lastname: Add background info on xyz
This makes it super easy to understand what was changed, who changed it, and where I can see the new content. I tried to do some of this in PR #168 but unfortunately it doesn't seem that the right data is available via the API.
Hope this is something you're able to add to your backlog. Thank you! 😄
The text was updated successfully, but these errors were encountered:
tyronedougherty
changed the title
Slack integration - provide more context about what was updated.
Feature request: Slack integration - provide more context about what was updated
Jun 3, 2023
Hey Gitbook team 👋
I really love that you have a Slack plugin, but right now it's not super useful outside of saying that "something was updated in
x
space". For example:This isn't very useful information. We want to keep our wider team informed of changes to our Gitbook docs - even if they don't have a seat on Gitbook. Right now this is a very manual process, because I have to go and summarise the changes each time we push a change.
Instead, it would be lovely if the Slack integration posted a message like:
This makes it super easy to understand what was changed, who changed it, and where I can see the new content. I tried to do some of this in PR #168 but unfortunately it doesn't seem that the right data is available via the API.
Hope this is something you're able to add to your backlog. Thank you! 😄
The text was updated successfully, but these errors were encountered: