summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axilleas@axilleas.me>2015-12-04 08:48:03 +0000
committerAchilleas Pipinellis <axilleas@axilleas.me>2015-12-04 08:48:03 +0000
commit14010b9efff6fda4ec5dda59611c74d29d2db3c7 (patch)
tree9d1a66a4a1542c120c7125af628525cf4d0ff9db
parente9d06903dab75129a0df63e686e18e85bfaeee8d (diff)
parent82ff9e65939d2da279b684cf378ca33e60eed66b (diff)
downloadgitlab-ce-14010b9efff6fda4ec5dda59611c74d29d2db3c7.tar.gz
Merge branch 'doc-ssh' into 'master'
Correction of markdown in SSH docs Correction of broken markdown in SSH docs See merge request !1900
-rw-r--r--doc/ssh/README.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/ssh/README.md b/doc/ssh/README.md
index 9753504ac8b..fe5b45dd432 100644
--- a/doc/ssh/README.md
+++ b/doc/ssh/README.md
@@ -15,7 +15,8 @@ Note: It is a best practice to use a password for an SSH key, but it is not
required and you can skip creating a password by pressing enter. Note that
the password you choose here can't be altered or retrieved.
-To generate a new SSH key, use the following commandGitLab```bash
+To generate a new SSH key, use the following command:
+```bash
ssh-keygen -t rsa -C "$your_email"
```
This command will prompt you for a location and filename to store the key
@@ -108,4 +109,4 @@ Note in the gitlab.com example above a username was specified to override the de
Due to the wide variety of SSH clients and their very large number of configuration options, further explanation of these topics is beyond the scope of this document.
Public SSH keys need to be unique, as they will bind to your account. Your SSH key is the only identifier you'll
-have when pushing code via SSH. That's why it needs to uniquely map to a single user.
+have when pushing code via SSH. That's why it needs to uniquely map to a single user. \ No newline at end of file