summaryrefslogtreecommitdiff
path: root/doc/ci/ssh_keys
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-01-30 15:09:15 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-01-30 15:09:15 +0000
commit536aa3a1f4b96abc4ca34489bf2cbe503afcded7 (patch)
tree88d08f7dfa29a32d6526773c4fe0fefd9f2bc7d1 /doc/ci/ssh_keys
parent50ae4065530c4eafbeb7c5ff2c462c48c02947ca (diff)
downloadgitlab-ce-536aa3a1f4b96abc4ca34489bf2cbe503afcded7.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/ssh_keys')
-rw-r--r--doc/ci/ssh_keys/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/ssh_keys/README.md b/doc/ci/ssh_keys/README.md
index bee1501aed8..62a8bb23e08 100644
--- a/doc/ci/ssh_keys/README.md
+++ b/doc/ci/ssh_keys/README.md
@@ -134,7 +134,7 @@ on, and use that key for all projects that are run on this machine.
Once done, try to login to the remote server in order to accept the fingerprint:
-```bash
+```shell
ssh example.com
```
@@ -150,7 +150,7 @@ connection would fail if the public keys would not match).
To find out the host keys of your server, run the `ssh-keyscan` command from a
trusted network (ideally, from the private server itself):
-```sh
+```shell
## Use the domain name
ssh-keyscan example.com