CODEWITHSUNDEEP
gitgithub
Jstation
Jstation

Reputation: 407

Cannot tag to GitHub because tag already exists

So I have a GitHub repository but I need to use SVN. Fortunately, GitHub has a SVN Bridge. I use TortoiseSVN with this as it's nice and easy and I love the colored icons in Explorer.

The problem is that GitHub is reporting that a tag already exists if the tag string forms part of an existing tag string.

For example. If I tag 1.0.0.alpha on an empty repository, that works fine. But if I then go on to tag 1.0.0, GitHub reports that 1.0.0 exists (which it obviously doesn't as the repository only contains the 1.0.0.alpha tag).

If the tag names are all completely unique (such as 1.0.1.alpha, 1.0.1.release), it works. Is there a bug in GitHub's SVN Bridge?

Importing the repository works fine. It's only when tagging that GitHub complains that a tag already exists when it doesn't.

Many thanks.

Upvotes: 0

Views: 558

Answers (1)

Jstation
Jstation

Reputation: 407

As @fredrik pointed out, this was a bug in GitHub's SVN Bridge. Using TortoiseSVN (GUI), tagging a release with a tag name string that formed part of an existing tag name string produced the 'tag already exists' error. However, tagging a release with a completely unique tag name string worked fine.

Using Slik SVN (command line) produced different results. Tagging a release with a tag name string that formed part of an existing tag name string prompted GitHub to add '/trunk' to the end of the release name. However, tagging a release with a completely unique tag name prompted GitHub to name the tag correctly.

I was able to use these tests to demonstrate to GitHub Support that there was a bug in the GitHub SVN Bridge code and I'm happy to say that they have now fixed that bug.

It appears that I can now tag releases just fine on GitHub using TortoiseSVN with no errors even if the tag name string forms part of an existing tag name string. So this issue appears to have been fixed by GitHub Support.

Upvotes: 1

Related Questions