-
Notifications
You must be signed in to change notification settings - Fork 3.8k
bugfix: Preserve https protocol when working with git #8703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: latest
Are you sure you want to change the base?
Conversation
|
Hm. Tests work fine, but in reality, nothing changed ( |
|
It seems also https://github.com/npm/pacote needs the same fix |
|
The |
When the URL explicitly contains https, do not try to switch to ssh. This change is necessary for [npm][3] to retain the protocol, please see the link and the referenced issues [here][1] and [here][2] reporting problems when using ssh instead of requested https. [1]: npm/cli#2610 [2]: npm/cli#4305 [3]: npm/cli#8703 Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
|
Fixed, tested, should work now. The fix in |
|
If you want to try the patched git clone -b fix/git-https-full --single-branch --depth=1 https://github.com/oldium/npm-cli.git
cd npm-cli
npm install
npm link
|
This prevents changing URLs from
httpsandgit+httpsintogit+ssh, but keeps the fall-back togit+sshwhen the protocol is not specified.The change in pacote is necessary in order to have this fully working.
References
Supersedes #5256
Blocked by npm/pacote#434
Fixes #4305
Fixes #2610