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
If the branch you are on is not up-to-date when you run tbump you may end up with something like this:
tbump
$ git push origin master v1.2.41-alpha-2 ... * [new tag] v1.2.41-alpha-2 -> v1.2.41-alpha-2 ! [rejected] master -> master (non-fast-forward)
and then you have a problem.
If you run git pull --rebase at this moment, but then the tag will get detached from the history.
git pull --rebase
Worse, if you have a continuous integration, you may trigger a deployment build with the tag in the wrong place.
A nice way to fix this issue is to push the branch and the tag in two separate commands (pushing the tag last).
The text was updated successfully, but these errors were encountered:
Push the tag after pushing the branch
3ecba48
This makes sure we don't create tags at the wrong place. Fixes #20
366860d
No branches or pull requests
If the branch you are on is not up-to-date when you run
tbump
you may end up with something like this:and then you have a problem.
If you run
git pull --rebase
at this moment, but then the tag will get detached from the history.Worse, if you have a continuous integration, you may trigger a deployment build with the tag in the wrong place.
A nice way to fix this issue is to push the branch and the tag in two separate commands (pushing the tag last).
The text was updated successfully, but these errors were encountered: