diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-30 18:08:27 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-30 18:08:27 +0300 |
| commit | 9376fdc13edb5fb822431df943fa088b6a273316 (patch) | |
| tree | f12ac6debd2c3efc59f1629062628f40996e752f /doc/ci/environments | |
| parent | 7c28a677895df5195ed6342921934734646c90c9 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/environments')
| -rw-r--r-- | doc/ci/environments/deployment_safety.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/environments/deployment_safety.md b/doc/ci/environments/deployment_safety.md index f8aa179b881..beb820a1da9 100644 --- a/doc/ci/environments/deployment_safety.md +++ b/doc/ci/environments/deployment_safety.md @@ -129,7 +129,7 @@ All project maintainers have access to production secrets. If you need to limit that can deploy to a production environment, you can create a separate project and configure a new permission model that isolates the CD permissions from the original project and prevents the original project's maintainers from accessing the production secret and CD configuration. You can -connect the CD project to your development projects by using [multi-project pipelines](../multi_project_pipelines.md). +connect the CD project to your development projects by using [multi-project pipelines](../pipelines/multi_project_pipelines.md). ## Protect `gitlab-ci.yml` from change |