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
When I do:;
bump2version subsubpatch .\setup.py
I got:
usage: bumpversion [-h] [--config-file FILE] [--verbose] [--list] [--allow-dirty] [--parse REGEX] [--serialize FORMAT] [--search SEARCH] [--replace REPLACE] [--current-version VERSION] [--no-configured-files] [--dry-run] --new-version VERSION [--commit | --no-commit] [--tag | --no-tag] [--sign-tags | --no-sign-tags] [--tag-name TAG_NAME] [--tag-message TAG_MESSAGE] [--message COMMIT_MSG] [--commit-args COMMIT_ARGS] part [file ...] bumpversion: error: the following arguments are required: --new-version
So please could you make the --new-version, really optional please!
bump2version -h usage: bumpversion [-h] [--config-file FILE] [--verbose] [--list] [--allow-dirty] [--parse REGEX] [--serialize FORMAT] [--search SEARCH] [--replace REPLACE] [--current-version VERSION] [--no-configured-files] [--dry-run] --new-version VERSION [--commit | --no-commit] [--tag | --no-tag] [--sign-tags | --no-sign-tags] [--tag-name TAG_NAME] [--tag-message TAG_MESSAGE] [--message COMMIT_MSG] [--commit-args COMMIT_ARGS] part [file ...]
bumpversion: v1.0.1 (using Python v3.10.9)
The text was updated successfully, but these errors were encountered:
Oh my god my code is finally working. I did not edit the .cfg file as expected. I gort the latest error.
For the future I suggest to considere using more warnings.
Up to you.
Sorry, something went wrong.
No branches or pull requests
When I do:;
bump2version subsubpatch .\setup.py
I got:
So please could you make the --new-version, really optional please!
bumpversion: v1.0.1 (using Python v3.10.9)
The text was updated successfully, but these errors were encountered: