Skip to content
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

Add backwards compatibility renaming for --protocol #26

Merged
merged 1 commit into from
May 1, 2024
Merged

Conversation

kzu
Copy link
Member

@kzu kzu commented 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 kzu added the bug Something isn't working label May 1, 2024
@kzu kzu enabled auto-merge (rebase) May 1, 2024 06:36
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 kzu force-pushed the dev/protocol branch from ab6544a to 0b2682f Compare May 1, 2024 06:37
@kzu kzu merged commit 402c58d into main May 1, 2024
8 checks passed
@kzu kzu deleted the dev/protocol branch May 1, 2024 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add backwards compatibility for breaking change from --protocol to --scheme
1 participant