-
Notifications
You must be signed in to change notification settings - Fork 84
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
Support Dry-run #125
Comments
Hello @kairos03. I'm open to this feature, and you're welcome to work on it. Implementation hint: Try subclassing Lines 85 to 102 in f1d2e3c
The put methods can be changed to register if puts were attempted. At the end you can check the result and return the appropriate exit code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before uploading a new package, I want to ensure that the version does not already exist.
To do this, I typically use the
--strict
option withupload
and immediatelydelete
the package afterward.However, I believe this is not the best approach. Could you introduce a
--dry-run
option to merely check if the new version upload will cause a conflict?If possible, I want to work on it. TX
The text was updated successfully, but these errors were encountered: