faq.md

@@ -29,6 +29,26 @@ Alternative solutions:
 
 The frontier between good and bad usage of the gitlab is fuzzy, but as there are a lot of users and projects on the gitlab, if too much people abuse the system we will have to put hard limits and restrictions on the gitlab usage, which will be annoying for everyone.
 
+## Should I choose "Clone with SSH" or "Clone with HTTPS"?
+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
+> 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 -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.
+
+[See also the following section](https://gitlab.inria.fr/siteadmin/doc/-/wikis/faq#how-to-not-have-to-type-a-password-for-every-git-operation)
+
 ## How to not have to type a password for every git operation
 
 First of all to avoid having to type login/password each type, the best is to use git over ssh rather than git over https (see below for git over http)