Closed 4lxDN3 closed 5 years ago
Tried with an empty .ssh
folder, still the same result.
I have a similar issue
Hello @4lxDN3 and @ivogrig The mgear_dist repository was configured using SSH credentials. This is not an issue for the main repo but for the submodules. We know this limitation and after long talk and research, we decided to keep it like this. So you need to use SSH at this point. or recreate your own mgear_dist My apologies for the inconvenience.
Too bad, you could reach a wider audience if you drop this restriction. Thanks for your answer.
@4lxDN3 is not really a restriction. You can configure your github account to use ssh key :) https://help.github.com/en/articles/connecting-to-github-with-ssh everybody can do it ;)
@miquelcampos But not everybody want to :p In a dream world, https should be enough to read and/or use an opensource project.
I would have to agree with @4lxDN3. You have probably discussed this heavy in the background with the developers, but its such a headache for newcomers to get through when all they wanna do is contribute.
@tokejepsen @4lxDN3 I don't remember all the reasons because we decided to keep this with SSH. For me, the main thing is time. If someone wants to join the dev team and take the responsibility to create an experimental dist repo base in Https (Don't change the current repo rights until we are sure) and test that all works. I more than happy to move to it.
@jdrese do you see any issue to move to https?
I am closing this one.
Describe the bug Executing the command
git clone https://github.com/mgear-dev/mgear_dist.git --recursive
does not work as expected. Some submodules do not materialize correctly.To Reproduce Execute the command WITHOUT any credentials in a terminal.
Additional information See attachment for a complete log.
clone_log.txt