"Updates were rejected because the tag already exists" when attempting to push in SourceTree

GitPushAtlassian Sourcetree

Git Problem Overview

When attempting to Push via Source Tree, I get the following error:

git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push -v --tags origin refs/heads/master:refs/heads/master 
Pushing to https://user@github.com/repo.git
To https://user@github.com/repo.git
 = [up to date]      master -> master
...
 ! [rejected]        example_tag -> example_tag (already exists)
updating local tracking ref 'refs/remotes/origin/master'
error: failed to push some refs to 'https://[email protected]/repo.git'
hint: Updates were rejected because the tag already exists in the remote.
Completed with errors, see above

I didn't make any changes to this tag as far as I know. How can I fix this?

Git Solutions

Solution 1 - Git

You should also be able to solve this in git bash (click on "Terminal" button in the Source Tree UI). Type:

git pull --tags

If you have conflicting tags, you can include the -f option in the command to override the local conflicting tags with their remote versions.

git pull --tags -f

Solution 2 - Git

If you have not made any local changes to the tag that you want to keep, then you can remove tag that was rejected because it already exists (example_tag in this case):

  1. Right-click the tag and choose to delete it (be sure to uncheck the Remove tag from all remotes checkbox).
  2. Choose the Fetch option (Fetch and store all tags locally does not have to be enabled).
  3. You should now have that tag that was just deleted back, and attempting to Push will no longer show that error message.

The reason this is common in SourceTree is because the Push all tags option is set to on by default. (Another way to hide this error is to uncheck that option.)

Solution 3 - Git

git pull --tags works really well but sometimes you can get an error even with this command. Example error message:

 ! [rejected]        example_tag      -> example_tag  (would clobber existing tag)

This can be solved with the command: git pull --tags -f

-f stands for force.

Source:

https://github.com/concourse/git-resource/issues/233

Solution 4 - Git

Uncheck push all tags at the bottom of the UI when you confirm your git push

Solution 5 - Git

Make sure you uncheck the "Push all tags" button while push.

enter image description here

Solution 6 - Git

In SourceTree, this seems to work:

  1. Click the Fetch icon
  2. Check "Fetch all tags"
  3. Click Ok
Categories
Recommended Git Solutions
Recommended Push Solutions
Recommended Atlassian Sourcetree Solutions

Previous Solution:

What is "Mounting" in React js?

JavascriptReactjs

Next Solution:

Kotlin with JPA: default constructor hell

HibernateJpaDefault ConstructorKotlin

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSensefulView Question on Stackoverflow
Solution 1 - GitbytedevView Answer on Stackoverflow
Solution 2 - GitSensefulView Answer on Stackoverflow
Solution 3 - GitOgglasView Answer on Stackoverflow
Solution 4 - GitJDev-GunsView Answer on Stackoverflow
Solution 5 - GitSudheer Kumar PalchuriView Answer on Stackoverflow
Solution 6 - GitJohn BergView Answer on Stackoverflow