From 0f950e9273d6b1b707918526a900c587ba934fa9 Mon Sep 17 00:00:00 2001 From: Mark HOEBEKE <mark.hoebeke@sb-roscoff.fr> Date: Thu, 17 Nov 2022 13:27:01 +0100 Subject: [PATCH] Finished the HTTP and SSH related sections. --- git-remote/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/git-remote/README.md b/git-remote/README.md index c423f33..d361601 100644 --- a/git-remote/README.md +++ b/git-remote/README.md @@ -60,10 +60,12 @@ An example of how to generate a key pair and view the public key is given in the  - This contents has to be copied to the GitLab SSH Key management page, accessible in the left panel of the User Settings page which can be displayed using `Edit profile` in the menu below the user badge (upper left corner). -The following screencast shows how to  +[This screencast](./media/gitlab-ssh.mp4) shows how to add an SSH key to GitLab + +The SSH private key must be present in the correct location on each machine (laptop, workstation) that will be used to access the GitLab repository. It is recommended to generate a key pair on each machine and to add each public key to GitLab. It avoids having multiple copies of a private key, and also allows to track which machine was used to access the repository. + -- GitLab