| ... | ... | @@ -33,18 +33,22 @@ The frontier between good and bad usage of the gitlab is fuzzy, but as there are |
|
|
|
We advise you to choose "Clone with SSH".
|
|
|
|
Indeed, the amount of data that can be transferred in an HTTP request or response is capped, which can cause issues when cloning large repositories over HTTPS.
|
|
|
|
If you encounter problems with git push on a repository cloned with git https, here is the command to change the remote configuration to SSH :
|
|
|
|
`$ git remote -v
|
|
|
|
```
|
|
|
|
$ git remote -v
|
|
|
|
origin https://gitlab.inria.fr/OWNER/REPOSITORY.git (fetch)
|
|
|
|
origin https://gitlab.inria.fr/OWNER/REPOSITORY.git (push)
|
|
|
|
|
|
|
|
git remote set-url origin git@gitlab.inria.fr:OWNER/REPOSITORY.git
|
|
|
|
```
|
|
|
|
`git remote set-url origin git@gitlab.inria.fr:OWNER/REPOSITORY.git`
|
|
|
|
|
|
|
|
```
|
|
|
|
$ git remote -v
|
|
|
|
|
|
|
|
Verify new remote URL
|
|
|
|
origin git@github.com:OWNER/REPOSITORY.git (fetch)
|
|
|
|
origin git@github.com:OWNER/REPOSITORY.git (push)
|
|
|
|
`
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
On the other hand, "Clone with HTTPS" can be useful in read-only mode.
|
|
|
|
|
| ... | ... | |
| ... | ... | |