summaryrefslogtreecommitdiff
path: root/doc/user/project/deploy_keys/index.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-05-31 18:09:56 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-05-31 18:09:56 +0000
commit9fcbd94aaa2c28096d84701e9474b589c1a1ddee (patch)
tree83a3806c67f8ff16d2a74d8963821a3c838c0a52 /doc/user/project/deploy_keys/index.md
parenteabd80f72f4f7d8e19b26526aa1f44c43d78e8b3 (diff)
downloadgitlab-ce-9fcbd94aaa2c28096d84701e9474b589c1a1ddee.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/deploy_keys/index.md')
-rw-r--r--doc/user/project/deploy_keys/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/deploy_keys/index.md b/doc/user/project/deploy_keys/index.md
index a6b54474a9e..c0bc97781b6 100644
--- a/doc/user/project/deploy_keys/index.md
+++ b/doc/user/project/deploy_keys/index.md
@@ -28,7 +28,7 @@ repository in automation, it's a simple solution.
A drawback is that your repository could become vulnerable if a remote machine is compromised
by a hacker. You should limit access to the remote machine before a deploy key is
enabled on your repository. A good rule to follow is to provide access only to trusted users,
-and make sure that the allowed users have [maintainer permissions or higher](../../permissions.md)
+and make sure that the allowed users have the [Maintainer role or higher](../../permissions.md)
in the GitLab project.
If this security implication is a concern for your organization,