Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/integrations/slack.md')
-rw-r--r--doc/user/project/integrations/slack.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/user/project/integrations/slack.md b/doc/user/project/integrations/slack.md
index e6f12c2532f..9e9f5b8297f 100644
--- a/doc/user/project/integrations/slack.md
+++ b/doc/user/project/integrations/slack.md
@@ -1,7 +1,7 @@
---
stage: Create
group: Ecosystem
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Slack Notifications Service
@@ -10,16 +10,16 @@ The Slack Notifications Service allows your GitLab project to send events
(such as issue creation) to your existing Slack team as notifications. Setting up
Slack notifications requires configuration changes for both Slack and GitLab.
-NOTE: **Note:**
+NOTE:
You can also use Slack slash commands to control GitLab inside Slack. This is the
separately configured [Slack slash commands](slack_slash_commands.md).
## Slack configuration
1. Sign in to your Slack team and [start a new Incoming WebHooks configuration](https://my.slack.com/services/new/incoming-webhook).
-1. Select the Slack channel where notifications will be sent to by default.
+1. Select the Slack channel where notifications should be sent to by default.
Click the **Add Incoming WebHooks integration** button to add the configuration.
-1. Copy the **Webhook URL**, which we will use later in the GitLab configuration.
+1. Copy the **Webhook URL**, which we use later in the GitLab configuration.
## GitLab configuration
@@ -36,7 +36,7 @@ separately configured [Slack slash commands](slack_slash_commands.md).
- To send messages to channels, enter the Slack channel names, separated by commas.
- To send direct messages, use the Member ID found in the user's Slack profile.
- NOTE: **Note:**
+ NOTE:
Usernames and private channels are not supported.
1. In **Webhook**, provide the webhook URL that you copied from the
@@ -47,7 +47,7 @@ separately configured [Slack slash commands](slack_slash_commands.md).
to send notifications for.
1. Click **Test settings and save changes**.
-Your Slack team will now start receiving GitLab event notifications as configured.
+Your Slack team now starts receiving GitLab event notifications as configured.
### Triggers available for Slack notifications
@@ -110,7 +110,7 @@ result = Net::HTTP.get(URI('https://<GITLAB URL>'));0
```
If GitLab is not trusting HTTPS connections to itself, then you may
-need to [add your certificate to GitLab's trusted certificates](https://docs.gitlab.com/omnibus/settings/ssl.html#install-custom-public-certificates).
+need to [add your certificate to the GitLab trusted certificates](https://docs.gitlab.com/omnibus/settings/ssl.html#install-custom-public-certificates).
If GitLab is not trusting connections to Slack, then the GitLab
OpenSSL trust store is incorrect. Some typical causes: overriding