Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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?

4 answers

I experience the same problem still with v2.3.5.0

The workaround of Serguei Mokhov is possible but very tedious. There should really be an option to move tags on remotes as well.

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.

Like AKrizan likes this

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?

Anyone...?

The only way I've found to move a remote tag is to delete it (from all remotes) and then recreate it again. SourceTree (as of 1.7.0.32509) on Windows is not capable of doing it. This documentation is incomplete, which simply covers a local case where it does work, but does not work for the remote updates with "Tag already exists".

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,390 views 4 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you