... | ... | @@ -26,13 +26,10 @@ and you should be shown a list with the parameters set above. |
|
|
|
|
|
**Creating an SSH key**
|
|
|
---------------------------
|
|
|
The default way for secure Git operation on OpenVT is the SSL protocol via https. This does not require depositing an SSH key. Only if you would like to use SSH (e.g. if you are using submodules), you need to deposit an SSH key on your profile. In this case, follow the instructions [here](https://openvt.eu/help/ssh/README#adding-an-ssh-key-to-your-gitlab-account); once you are done, test your setup with
|
|
|
The default way for secure Git operation on OpenVT is the SSL protocol via https. Therefore, there is no need to deposit an SSH key on OpenVT.
|
|
|
|
|
|
```bash
|
|
|
ssh -T git@openvt.eu
|
|
|
```
|
|
|
|
|
|
**Cloning an OpenVT repository with https/SSH**
|
|
|
**Cloning an OpenVT repository with https**
|
|
|
--------------------------------------------------------------------------
|
|
|
Now we need to create your first local clone of a Gitlab repository. First, pick a repository on the OpenVT platform that you would like to clone (as a test, you can use the manual_and_guidelines repository, or just start your own private project). Browse to the corresponding repository screen (e.g., [this one](https://openvt.eu/platform_manual_and_guidelines/manual_and_guidelines)), find the blue "clone" button and copy the link for https cloning (the link starts with https://).
|
|
|
|
... | ... | @@ -54,17 +51,13 @@ git clone <https_cloning_link> |
|
|
```
|
|
|
(replace <https_cloning_link> with the link that you have copied from the blue button on the repository web site). You will be prompted for your OpenVT username and password, if the project you are about to clone requires any access privileges.
|
|
|
|
|
|
If you prefer cloning via SSH, type instead
|
|
|
```bash
|
|
|
git clone <SSH_cloning_link>
|
|
|
```
|
|
|
You should be prompted to enter the pass phrase of your SSH key which you have (hopefully) memorised earlier.
|
|
|
|
|
|
If in either case the process was successful, the clone of the repository should appear in the current directory, which you can check by typing
|
|
|
If the process was successful, the clone of the repository should appear in the current directory, which you can check by typing
|
|
|
```bash
|
|
|
ls -l -tr
|
|
|
```
|
|
|
which shows you a list of all files and subdirectories in that directory in reverse time order. The clone should be shown as directory on the bottom of the list with the same as the cloned Project. You can now work with these files in this folder like with any other file on your computer.
|
|
|
which shows you a list of all files and subdirectories in that directory in reverse time order. The clone should be shown as directory on the bottom of the list with the same as the cloned Project. You can now work with these files in this folder like with any other file on your computer.
|
|
|
|
|
|
If for some reason,
|
|
|
|
|
|
Working with a cloned repository: pull and push
|
|
|
-------------------------------------------------------
|
... | ... | @@ -84,7 +77,7 @@ where you replace commit message with a meaningful description of the modificati |
|
|
```bash
|
|
|
git push origin master
|
|
|
```
|
|
|
this will prompt you for your pass phrase (or user name and password, for SSL) and upload your changes to OpenVT. If there is only one branch in your repository, you can skip the "origin master" options. On the other hand, if there are different branches, you can replace "master" with the branch to which you would like to push. Your modifications will now be accessible on OpenVT to anyone who has access to the project under consideration.
|
|
|
this will prompt you for your user name and password and upload your changes to OpenVT. If there is only one branch in your repository, you can skip the "origin master" options. On the other hand, if there are different branches, you can replace "master" with the branch to which you would like to push. Your modifications will now be accessible on OpenVT to anyone who has access to the project under consideration.
|
|
|
|
|
|
Repeat this work flow every time that you would like to do modifications on the contents of your OpenVT repository.
|
|
|
|
... | ... | |