Commit 04aa56df authored by Justin Ho's avatar Justin Ho

Update docs with new copy

parent f3dcb70e
...@@ -54,7 +54,7 @@ Then fill in the integration configuration: ...@@ -54,7 +54,7 @@ Then fill in the integration configuration:
To change the bot's username, provide a value. To change the bot's username, provide a value.
- **Notify only broken pipelines**: If you enable the **Pipeline** event, and you want - **Notify only broken pipelines**: If you enable the **Pipeline** event, and you want
notifications about failed pipelines only. notifications about failed pipelines only.
- **Branches to be notified**: The branches to send notifications for. - **Branches for which notifications are to be sent**: The branches to send notifications for.
- **Labels to be notified**: (Optional) Labels required for the issue or merge request - **Labels to be notified**: (Optional) Labels required for the issue or merge request
to trigger a notification. Leave blank to notify for all issues and merge requests. to trigger a notification. Leave blank to notify for all issues and merge requests.
- **Labels to be notified behavior**: When you use the **Labels to be notified** filter, - **Labels to be notified behavior**: When you use the **Labels to be notified** filter,
......
...@@ -45,7 +45,7 @@ to control GitLab from Slack. Slash commands are configured separately. ...@@ -45,7 +45,7 @@ to control GitLab from Slack. Slash commands are configured separately.
1. (Optional) In **Username**, enter the username of the Slack bot that sends 1. (Optional) In **Username**, enter the username of the Slack bot that sends
the notifications. the notifications.
1. Select the **Notify only broken pipelines** checkbox to notify only on failures. 1. Select the **Notify only broken pipelines** checkbox to notify only on failures.
1. In the **Branches to be notified** dropdown, select which types of branches 1. In the **Branches for which notifications are to be sent** dropdown, select which types of branches
to send notifications for. to send notifications for.
1. Leave the **Labels to be notified** field blank to get all notifications, or 1. Leave the **Labels to be notified** field blank to get all notifications, or
add labels that the issue or merge request must have to trigger a add labels that the issue or merge request must have to trigger a
......
...@@ -21,7 +21,7 @@ In GitLab: ...@@ -21,7 +21,7 @@ In GitLab:
1. Select the checkboxes corresponding to the GitLab events you want to receive in Unify Circuit. 1. Select the checkboxes corresponding to the GitLab events you want to receive in Unify Circuit.
1. Paste the **Webhook URL** that you copied from the Unify Circuit configuration step. 1. Paste the **Webhook URL** that you copied from the Unify Circuit configuration step.
1. Select the **Notify only broken pipelines** checkbox to notify only on failures. 1. Select the **Notify only broken pipelines** checkbox to notify only on failures.
1. In the **Branches to be notified** dropdown, select which types of branches to send notifications for. 1. In the **Branches for which notifications are to be sent** dropdown, select which types of branches to send notifications for.
1. Select `Save changes` or optionally select **Test settings**. 1. Select `Save changes` or optionally select **Test settings**.
Your Unify Circuit conversation now starts receiving GitLab event notifications. Your Unify Circuit conversation now starts receiving GitLab event notifications.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment