-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 --skip-existing option to poetry publish #2254
Comments
would you accept a patch that adds this? |
@davidszotten feel free to propose an implementation for this. You can either create a draft PR to discuss implementation or mention how you would want to approach this here. A few things that comes to mind:
Happy to help review etc. |
i would probably do something similar to twine (heuristics for a few package index implementations that try to detect this particular error) i explicitly don't want to ignore all errors, only "this file already exists" |
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
Any hope to get this feature? Can't find discussion on what happened to above.. 😟 |
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
How can I help get this feature merged? |
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
Even tho I really like this project I'm forced to use twine for publishing generated clients :( This would be awesome to merge! |
I agree that this feature would be great. The PR looks good too me (although I did not check all possible responses :) ). |
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves python-poetry#2254
* dry_run is never None * add --skip-existing to publish add `--skip-existing` option to publish command to continue if an upload fails due to the file already existing. this is helpful in e.g. ci settings. resolves #2254
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature Request
The twine tool for publishing to PyPi style repos has a very useful option
--skip-existing
for thetwine upload
command. This option basically says "don't error out if a file already exists on PyPi, continue to the next".This is super useful in a number of cases, including with CI/CD pipelines where, on branching, the pipeline will trigger a build for the new branch, but of course that first build will already have a corresponding package in PyPi as the commit it's being built from has already been built on the branch that the new branch was created from. In that case, it's fine for the pipeline to fail to upload the file as it already exists.
There are various other use cases for this flag. Could we have an equivalent flag for
poetry publish
?The text was updated successfully, but these errors were encountered: