Add documentation for Slack Workspace #3005
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
pipelines
eleanorakh
force-pushed
the
slack-updates
branch
from
0d3f6a1
to
4d7c39a
Compare
There was a problem hiding this comment.
The following is no longer true with the new method:
docs/pages/integrations/slack.md
Line 6 in 4d7c39a
I wonder if it's worth breaking this whole integration into a separate page?
I also wonder if we should remove the section on "Legacy slack" now that we've added yet another version!
| @@ -7,7 +7,21 @@ Configuring a Slack notification service will authorize access for your desired | |||
|
|
|||
| Setting up a Notification Service requires Buildkite organization admin access. | |||
|
|
|||
| ## Adding a notification service | |||
| ## Adding notification services | |||
| There are two ways to add notification services: workspace-wide and channel-specific. We reccomend using a workspace. Using a workspace only requires a single authorization for the entire workspace, allowing you to connect channels via YAML rather than multiple notifications services. The migration to a Workspace will not impact current integration implementation. | |||
There was a problem hiding this comment.
I reckon it's also worth calling out that the workspace integration adds support for Slack mentions, specifically because we request an additional scope to read user email addresses.
| @@ -7,7 +7,21 @@ Configuring a Slack notification service will authorize access for your desired | |||
|
|
|||
| Setting up a Notification Service requires Buildkite organization admin access. | |||
|
|
|||
| ## Adding a notification service | |||
| ## Adding notification services | |||
| There are two ways to add notification services: workspace-wide and channel-specific. We reccomend using a workspace. Using a workspace only requires a single authorization for the entire workspace, allowing you to connect channels via YAML rather than multiple notifications services. The migration to a Workspace will not impact current integration implementation. | |||
There was a problem hiding this comment.
Suggested change
| There are two ways to add notification services: workspace-wide and channel-specific. We reccomend using a workspace. Using a workspace only requires a single authorization for the entire workspace, allowing you to connect channels via YAML rather than multiple notifications services. The migration to a Workspace will not impact current integration implementation. | |
| There are two ways to add notification services: workspace-wide and channel-specific. We recommend using a workspace. Using a workspace only requires a single authorization for the entire workspace, allowing you to connect channels via YAML rather than multiple notifications services. The migration to a Workspace will not impact current integration implementation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're in the process of rolling out some changes to the Slack Integration. This PR addresses: