I have recently tried using the Github Desktop (GD) app for streamlining my attempts to develop (it links with VS code and has a GUI, which is nice for someone new like me, or other potentially new developers). I noticed a problem with the cloning ability of GD to handle github links that require SSH passwords, in that it will just never ask you for a password and will instead just hang up on the various git@github such as this one from the actual clone I did the other day git@github.com:OpenChemistry/avogadro-i18n.git.
If the links like this are all replaced with the https://github.com/ version, this won’t be an issue anymore. I am not sure how that is handled, but I am certain that a certain professor from UPitt is capable of getting that one done (wink wink @ghutchis)
Well, I’m not going to change them because I prefer use of SSH… but I think I’ve found a way to do relative submodules.
For yourself, you can either git clone the individual directories, or look at something like this to change the protocol for the submodules:
But looking at openchemistry/.gitmodules, HTTPS is already being used for almost all of the submodules…
Only fragments, avogadro-i18n, and jupyter-examples use SSH links. And when I use git clone --recursive https://github.com/OpenChemistry/openchemistry.git, without ssh authentication set up, only those three submodules fail (though that unfortunately derails the whole recursive clone).
What’s the advantage of using SSH for those specific submodules? And, assuming you use the recursive clone/submodule strategy yourself, does your git setup currently use SSH for authentication for all the submodules even though they are listed in .gitmodules with their HTTPS addresses?
1 Like
No, that would be a bug. Let me go fix them up. They’re all supposed to be consistent.