Add backwards compatibility for breaking change from --protocol to --scheme #25
Labels
bug
Something isn't working
Comments
kzu
added a commit
that referenced
this issue
May 1, 2024
Which is now --scheme. To make the option consistent across all three commands, we renamed --protocol to --scheme so we could always use the shorthand -s regardless of whether there was a -p|--password option too. This caused older invocations to break since the protocol would be null/empty and thus a matching provider was not found (i.e. for github). Fixes #25
kzu
added a commit
that referenced
this issue
May 1, 2024
Which is now --scheme. To make the option consistent across all three commands, we renamed --protocol to --scheme so we could always use the shorthand -s regardless of whether there was a -p|--password option too. This caused older invocations to break since the protocol would be null/empty and thus a matching provider was not found (i.e. for github). Fixes #25
kzu
added a commit
that referenced
this issue
May 1, 2024
Which is now --scheme. To make the option consistent across all three commands, we renamed --protocol to --scheme so we could always use the shorthand -s regardless of whether there was a -p|--password option too. This caused older invocations to break since the protocol would be null/empty and thus a matching provider was not found (i.e. for github). Fixes #25
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
To make the option consistent across all three commands, we renamed
--protocolto--schemeso we could always use the shorthand-sregardless of whether there was a-p|--passwordoption too.This caused older invocations to break since the protocol would be null/empty and thus a matching provider was not found (i.e. for github).
Version Info
Appeared in v2.4.1
The text was updated successfully, but these errors were encountered: