diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-01-31 03:14:49 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-01-31 03:14:49 +0300 |
| commit | 60ee9c4bdc1d63ca9a25bd7ef22180cc85505a59 (patch) | |
| tree | d5ab6da6c3ef074a552ea22d15e9519c79ab3803 /doc/ci/chatops | |
| parent | bd21e1c5886c5bd0fb981b2817bd81823b9f1e2c (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/chatops')
| -rw-r--r-- | doc/ci/chatops/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/chatops/index.md b/doc/ci/chatops/index.md index 698b467a813..c785e2f29ea 100644 --- a/doc/ci/chatops/index.md +++ b/doc/ci/chatops/index.md @@ -43,7 +43,7 @@ job completes: [Slack API](https://api.slack.com/) to send data to the channel. To use the `run` command, you must have at least the -[Developer role](../../user/permissions.md#project-members-permissions). +Developer role. If a job shouldn't be able to be triggered from chat, you can set the job to `except: [chat]`. ## Best practices for ChatOps CI jobs @@ -55,7 +55,7 @@ functions available. Consider these best practices when creating ChatOps jobs: of the standard CI pipeline. - If the job is set to `when: manual`, ChatOps creates the pipeline, but the job waits to be started. - ChatOps provides limited support for access control. If the user triggering the - slash command has at least the [Developer role](../../user/permissions.md#project-members-permissions) + slash command has at least the Developer role in the project, the job runs. The job itself can use existing [CI/CD variables](../variables/index.md#predefined-cicd-variables) like `GITLAB_USER_ID` to perform additional rights validation, but |