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
upload
Currently it's very vague how to upload a package using pixi upload.
pixi upload
We should improve the UX on prefix.dev. Provide help text what the proper command should be for different tools.
Currently you have to use:
pixi upload https://prefix.dev/api/v1/upload/<channel_name> <filename>
This is user-unfriendly and hard to discover.
Uploading to any URL that accepts the request is enough for the command to think it succeeded. For instance:
pixi upload https://prefix.dev/channels/<channel_name> <package> -vvv
Just succeeds but doesn't actually do anything.
The text was updated successfully, but these errors were encountered:
pixi
You could just incorporate the upload CLI from rattler-build and put it into rattler, similar as with auth login.
auth login
Sorry, something went wrong.
No branches or pull requests
Currently it's very vague how to upload a package using
pixi upload
.We should improve the UX on prefix.dev. Provide help text what the proper command should be for different tools.
Currently you have to use:
This is user-unfriendly and hard to discover.
Uploading to any URL that accepts the request is enough for the command to think it succeeded. For instance:
Just succeeds but doesn't actually do anything.
The text was updated successfully, but these errors were encountered: