4 ms·
And in consequence although many people will experience it no longer working, it might still "work" for you (or it might never have "worked") since anybody who
by tialaramex 5y ago
And in consequence although many people will experience it no longer working, it might still "work" for you (or it might never have "worked") since anybody who is between you and GitHub can decide what happens instead.
If you've insisted on building something that insists on using git:// this way, you can proxy it to the safer supported system seamlessly, since you had no way to know before it was correct and you'll have no way to know if the proxy worked either. Somebody might already make a tool to do that, if not you could roll your own.
- WorldMaker 5y agoGit itself has a config flag to tell it to always use https:// https:// instead of git://. It's often been recommended for Windows users of git as sometimes the only way out of some peculiar submodule holes (on a platform where SSH was a second class citizen for many decades). git config --global url."https://".insteadOf https://".insteadOf git:// There are versions of that config line more specific to individual hosts if you didn't want to blanked cover every git host, but it's probably a good idea at this point to instead ask those other hosts if they would consider adding https:// https:// support.