After local "move tag", can't push with tags to remote

Question

Source Tree offers an option to move a tag if I try to tag current commit using existing tag. I did that locally, but now when I try to push to bitbucket, I get the error that tag already exists.

hint: Updates were rejected because the tag already exists in the remote.

Here's the complete log of the push attempt

git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push -v --tags origin master:master 
Pushing to git@bitbucket.org:*****
To git@bitbucket.org:****
 = [up to date]      master -> master
 = [up to date]      v4.0 -> v4.0
 ! [rejected]        4.0.1 -> 4.0.1 (already exists)
updating local tracking ref 'refs/remotes/origin/master'
error: failed to push some refs to 'git@bitbucket.org:****'
hint: Updates were rejected because the tag already exists in the remote.
Completed with errors, see above

How to reconcile this problem?

Tushar Raut · Answer

This method worked for me.

https://stackoverflow.com/questions/31929667/updates-were-rejected-because-the-tag-already-exists-when-attempting-to-push-i

Hope it helps you too.

Have a good day!

rando@extra-nice · Answer

For me, this works when done in the command line, but it doesn't when I make it a custom action. It says it failed with errors, but no errors are shown (and it doesn't do what it should).

Any ideas what could cause this?

Martin Widmer_pvt1qi · Answer

As mentioned in another forum (https://jira.atlassian.com/browse/SRCTREE-3018), there is another workaround using the git command line to force push the tags:

git push origin --tags -f

If you're often moving tags around, I suggest creating a custom action for this:

Script to run: git

Parameters: push origin --tags -f

Since this only affects tags, there is not as much danger involved as in other forced commands.