Summary
WHen I was trying to push to my project using git push https://gitlab.com/___/___.git:master -u via Python3 (I think using Python3 isn’t a problem, and I need to use Python3) using subprocess.Popen().
Steps to reproduce
- Clone random repo from GitLab (I tested it on another repo, same problem) using git on CLI
- Push to GitLab using git on CLI
Note: python3lover / test was an empty repo
What is the current bug behavior?
git says:
fatal: https://python3lover@gitlab.com/python3lover/test.git:master/info/refs not valid: is this a git repository?
What is the expected correct behavior?
I sould see git pushing to my remote repo.
Relevant logs and/or screenshots
Whole Output of git
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:
git config --global push.default matching
To squelch this message and adopt the new behavior now, use:
git config --global push.default simple
When push.default is set to 'matching', git will push local branches
to the remote branches that already exist with the same name.
In Git 2.0, Git will default to the more conservative 'simple'
behavior, which only pushes the current branch to the corresponding
remote branch that 'git pull' uses to update the current branch.
See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)
fatal: https://python3lover@gitlab.com/python3lover/test.git:master/info/refs not valid: is this a git repository?
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)
Results of GitLab application Check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
/label ~bug