diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-26 18:09:04 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-26 18:09:04 +0300 |
| commit | ee24c7d68f57a67754a5d1e2ea99f688029d14bd (patch) | |
| tree | 8391744a26dd3f77c4bb1bbb55672ba0e066d969 /doc/user/project/deploy_keys | |
| parent | a1c0b634f78f51389fd3ec390a1803afa3de49a2 (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 | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/deploy_keys/index.md b/doc/user/project/deploy_keys/index.md index e87c5f57fc1..fc88535dc77 100644 --- a/doc/user/project/deploy_keys/index.md +++ b/doc/user/project/deploy_keys/index.md @@ -99,7 +99,7 @@ To create a public deploy key: 1. Select **New deploy key**. 1. Complete the fields. - Use a meaningful description for **Name**. For example, include the name of the external host - or application that will use the public deploy key. + or application that uses the public deploy key. You can modify only a public deploy key's name. @@ -148,7 +148,7 @@ What happens to the deploy key when it is disabled depends on the following: ### Deploy key cannot push to a protected branch -There are a few scenarios where a deploy key will fail to push to a +There are a few scenarios where a deploy key fails to push to a [protected branch](../protected_branches.md). - The owner associated to a deploy key does not have access to the protected branch. |