You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But there is also GIT_SSH env. var honored by standard git. The GIT_SSH_COMMAND should use GIT_SSH (and quoted) instead of ssh when GIT_SSH is non-empty.
npm will no longer manually set `GIT_ASKPASS` or `GIT_SSH_COMMAND` if it finds those values already defined in the user's git config.
## References
npm/cli#2891#193#129
---------
Co-authored-by: pacotedev <i+pacotedev@izs.me>
Is there an existing issue for this?
Current Behavior
Currently
GIT_SSH_COMMAND
has hardcodedssh
path in https://github.com/npm/git/blob/v4.0.4/lib/opts.js#L5But there is also
GIT_SSH
env. var honored by standard git. TheGIT_SSH_COMMAND
should useGIT_SSH
(and quoted) instead ofssh
whenGIT_SSH
is non-empty.Will fix npm/cli#2891 as I can confirm npm/cli#2891 (comment) fixes the problem.
Expected Behavior
GIT_SSH
other thanssh
/empty is honored.The text was updated successfully, but these errors were encountered: