We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Registering a repository using the --repo "owner:repo1,owner:repo2" option fails.
--repo "owner:repo1,owner:repo2"
To Reproduce
Steps to reproduce the behavior:
medic repo register --provider github --repo "owner:repo1,owner:repo2"
I wasn't sure of the correct syntax but tried the following options none of which worked - rdimitrov:dex, rdimitrov:rdimitrov/dex, root:rdimitrov/dex.
rdimitrov:dex
rdimitrov:rdimitrov/dex
root:rdimitrov/dex
Expected behavior
Have a successful registration of that repository.
Screenshots
After step 3, this is the output that I get -
Error registering repositories: rpc error: code = InvalidArgument desc = InvalidArgument indicates client specified an invalid argument.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
rdimitrov
Successfully merging a pull request may close this issue.
Describe the bug
Registering a repository using the
--repo "owner:repo1,owner:repo2"
option fails.To Reproduce
Steps to reproduce the behavior:
medic repo register --provider github --repo "owner:repo1,owner:repo2"
I wasn't sure of the correct syntax but tried the following options none of which worked -
rdimitrov:dex
,rdimitrov:rdimitrov/dex
,root:rdimitrov/dex
.Expected behavior
Have a successful registration of that repository.
Screenshots
After step 3, this is the output that I get -
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: