diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-28 21:08:00 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-28 21:08:00 +0300 |
| commit | ff82d09c6a72dc280aed1bba50553e7f1f169f0f (patch) | |
| tree | 13c41cacb07b0bff84536235e3d77d9db057d8c2 /doc/user/project/deploy_keys | |
| parent | 24623a974348595d33cc9be6881b285a026ff13b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/deploy_keys')
| -rw-r--r-- | doc/user/project/deploy_keys/index.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/user/project/deploy_keys/index.md b/doc/user/project/deploy_keys/index.md index 5bd19fec0ba..60cad9d6fe9 100644 --- a/doc/user/project/deploy_keys/index.md +++ b/doc/user/project/deploy_keys/index.md @@ -40,7 +40,6 @@ A deploy key is given a permission level when it is created: You can change a deploy key's permission level after creating it. Changing a project deploy key's permissions only applies for the current project. -Although a deploy key is a secret that isn't associated with a specific user, GitLab authorizes the creator of the deploy key if the Git-command triggers additional processes. For example: - When a deploy key is used to push a commit to a [protected branch](../protected_branches.md), |