For me, release-prepare
seems to be pushing three times:
- After committing the POM updated to the new release version, it's running
git push
with no arguments, to push that commit.
- After tagging, it's running
git push origin <tagname>
, which is what should push the tag.
- After committing the POM updated to the new snapshot version, it's running
git push
with no arguments again.
Given that it's explicitly specifying origin
for the tag push, it may only successfully push the tags if your git-remote alias is actually called origin
.
To see what yours are called, run git remote -v
.
Note also that git push
without arguments may default to something other than origin
, depending on your repository config - i.e. it may have been trying to push commits to one place and tags to another. See here for where those defaults come from:
http://www.kernel.org/pub/software/scm/git/docs/git-push.html#REMOTES