diff options
| author | Adam Niedzielski <adamsunday@gmail.com> | 2017-03-20 16:49:05 +0300 |
|---|---|---|
| committer | Adam Niedzielski <adamsunday@gmail.com> | 2017-03-20 16:49:05 +0300 |
| commit | d29f90b54c11620b0b1879fceb1372300be00d8e (patch) | |
| tree | 8f2d9eed1e65c64c85fbdcd7f9efe7777a9ed513 /doc/ssh | |
| parent | 915af2dc5ae903d0007f5c2c75518483e00ab610 (diff) | |
Update deploy keys documentation
Diffstat (limited to 'doc/ssh')
| -rw-r--r-- | doc/ssh/README.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ssh/README.md b/doc/ssh/README.md index 678f5199b02..cf28f1a2eca 100644 --- a/doc/ssh/README.md +++ b/doc/ssh/README.md @@ -170,12 +170,12 @@ Integration (CI) server. By using deploy keys, you don't have to setup a dummy user account. If you are a project master or owner, you can add a deploy key in the -project settings under the section 'Deploy Keys'. Press the 'New Deploy -Key' button and upload a public SSH key. After this, the machine that uses +project settings under the section 'Repository'. Specify a title for the new +deploy key and paste a public SSH key. After this, the machine that uses the corresponding private SSH key has read-only or read-write (if enabled) access to the project. -You can't add the same deploy key twice with the 'New Deploy Key' option. +You can't add the same deploy key twice using the form. If you want to add the same key to another project, please enable it in the list that says 'Deploy keys from projects available to you'. All the deploy keys of all the projects you have access to are available. This project |