-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1.6.0, 2.0.5
-
None
-
Severity 3 - Minor
A tag was added to the last commit on the develop branch before the merge to the master branch. I tried to move the tag to the master commit. It was successful on the local git repo but then failed when moving on the remote repo at Bitbucket.
In the Add Tag window, I selected the 0.60 tag from the popup menu, selected the 'Specified commit' button and picked the merge commit on the master branch (f8fba4). Enabled the Push tag checkbox, expanded the Advanced Options and enabled the Move Existing Tag checkbox. Clicked Add and got the following in the log window.
git -c diff.mnemonicprefix=false -c core.quotepath=false tag -a -m -f 0.60 f8fba4f2e5f537d1d7d4b210c853bb587cdc67d6 Updated tag '0.60' (was 2d7d6bd) git -c diff.mnemonicprefix=false -c core.quotepath=false push -v Bitbucket refs/tags/0.60 Pushing to git@bitbucket.org:InsomniacSoftware/acdc.git To git@bitbucket.org:InsomniacSoftware/acdc.git ! [rejected] 0.60 -> 0.60 (already exists) error: failed to push some refs to 'git@bitbucket.org:InsomniacSoftware/acdc.git' hint: Updates were rejected because the tag already exists in the remote. Completed with errors, see above
Note that the Updated tag line says (was 2d7d6bd) however, I don't have a commit with that hash in the entire repo history. Do tags have their own tracking hashes?
I was able to resolve this issue by removing the 0.60 tag from the local and remote repos then add the tag again onto the proper commit.
[SRCTREE-1676] Fails to move remote tag
| Workflow | Original: JAC Bug Workflow v3 [ 3370938 ] | New: SRCTREE JAC Bug Workflow [ 3737537 ] |
| Workflow | Original: SourceTree Bug Workflow [ 538764 ] | New: JAC Bug Workflow v3 [ 3370938 ] |
| Status | Original: Verified [ 10005 ] | New: Gathering Impact [ 12072 ] |
| Symptom Severity | New: Minor [ 14432 ] |
| Status | Original: Open [ 1 ] | New: Verified [ 10005 ] |
| Affects Version/s | New: 2.0.5 [ 50690 ] |
On Mac the force option does seem to have no effect for the tagging dialog. Still the bug is present on both Win and Mac versions.
Sorin Sbarnea (Citrix)
added a comment - - edited On Mac the force option does seem to have no effect for the tagging dialog. Still the bug is present on both Win and Mac versions. Is anyone from Atlassian really working on SourceTree? This bug is going to be 2 years old really soon and is not even marked as verified. I can confirm that it does reproduce with Version 2.0.5.2 (2.0.5.2).
If anyone encounters the same bug, do not forget to raise a support ticket on https://support.atlassian.com and indicate this bug. This seems to be the (only) way of getting bug fixed.
Sorin Sbarnea (Citrix)
added a comment - - edited Is anyone from Atlassian really working on SourceTree? This bug is going to be 2 years old really soon and is not even marked as verified. I can confirm that it does reproduce with Version 2.0.5.2 (2.0.5.2).
If anyone encounters the same bug, do not forget to raise a support ticket on https://support.atlassian.com and indicate this bug. This seems to be the (only) way of getting bug fixed. 
Eugenio Viudez García
added a comment - I have the same problem. This option worked properly 2 o 3 months ago, so should be a problem of the new versions.
Eugenio Viudez García
added a comment - I have the same problem. This option worked properly 2 o 3 months ago, so should be a problem of the new versions. 
Paul Ellis
added a comment - Happens on Windows version 1.3.3.0 too
Also got the same Problem. Happens with GitLab / Stash as server as well. Seems to be definitive a SourceTree Issue