While trying to clone an already existing repository from gitlab into my local drive. I used the format
$ git clone https://github.com/libgit2/libgit2 mylibgit
Gitlab actually requires a user when using deploy tokens. For me, this was caused by mixing in ssh syntax as http://<user>:<pass>@gitlab.com:repo
instead of gitlab.com/repo
.
if you change your remote from using ssh to https and accidentally leave a colon in the string - you will a message like this. It's a confusing message, but it makes sense once you understand the source of the problem.
For gitlab, you don't need to specify the user.
Replace it by an https url based on your GitLab account name.
cd /path/to/your/repo
git remote set-url origin https://gitlab.com/<username>/<yourProjectName.git>
git push -u origin master
Note:
trying to clone an already existing repository from gitla
This contradict "git clone https://github.com/libgit2/libgit2
", since this is a GitHub url, not a GitLab one.
I had similar problem. Just corrected(removed git@ and port number) URL in .git/config file and it worked.
[remote "origin"] url = https://git@gitlab.com:xxxxx/yyyyyy/
To
[remote "origin"] url = https://gitlab.com/yyyyyy/
I later found the problem, I was not typing cd /path/to/your/repo
at the beginning.
I was actually typing gitlab
instead of Github
.
Thanks.