Correction of markdown in SSH docs
This commit is contained in:
parent
ef2bc0f0bf
commit
82ff9e6593
|
@ -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.
|
Loading…
Reference in New Issue