Open peritus opened 10 years ago
Hello, I'm trying bumpversion for the first time and found myself at this issue and #115 because of a similar use case. Like #115, I'd like to use the following workflow:
What about making "tag" a separate command? For instance, I could bumpversion
and make changes and commits. When I'm finally done, I then run bumpversion tag
to have it automatically add a git tag with the most recent version. This could work well, as bumpversion already exits if the working directory isn't clean, so it could use the most recent commit as the target for the tag.
Thank you for your efforts and making bumpversion available.
Some workflows require an intermediate step between changing the version strings in the files and the actual commit or tag. The current state of the implementation is all or nothing.
The workaround executing bumpversion, changing stuff and amend-commit-ing doesn't work because the tagged commit is the original, unamended one and then you'd have to delete that tag and tag the new commit and why are you using this again?
Usecases:
Could work something like this:
or
or
...