-
Notifications
You must be signed in to change notification settings - Fork 792
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
Request: add an option to force tag replacement #846
Open
pluce opened this issue
Nov 3, 2021
· 0 comments
· Fixed by absolute-version/commit-and-tag-version#5 · May be fixed by #847
Open
Request: add an option to force tag replacement #846
pluce opened this issue
Nov 3, 2021
· 0 comments
· Fixed by absolute-version/commit-and-tag-version#5 · May be fixed by #847
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe my use-case is weird but I often need to re-apply
standard-version
changelog generation when crafting my release, for many reasons: last minute bug fixes, forgotten pull requests, etc.My workflow is:
standard-version
to bump version, generate changelog, commit the file, add tagThe problem appears on the last step, as I'd like to use
standard-version --skip.bump
to just update the Changelog without creating a new version, but it fails on the tagging step because tag already exists. I may not use--skip.tag
because I do want the tag to be updated to the latest commit.That's why I'd like to have an option that allows me to move the existing version tag to the latest commit.
PR incoming !
The text was updated successfully, but these errors were encountered: