Implicit tagging happening on an old commit and the tag name is same as the branch name.
Recently we have observed that one of the old commit is getting tagged exactly with the same branch name that causes bit bucket conflicts and does not allow the us to push any code. We are struggling to figure out how these tags are getting generated as these are not being done by any of the developers. We use jenkins for deployment.
Any help will be deeply appreciated.
Hi @Ankit Gupta ,
Do you see this tag in the remote Bitbucket repo? Or in a clone of this repo elsewhere?
One possibility is that this tag in this old commit exists in one of the developers' local clone of this repo, and then gets pushed to the Bitbucket repo.
My suggestion would be to ask the developers working on this repo to check the tags in their local clone
This will list all tags that their local clone has, and they can check whether this specific tag exists.
If it does, they can remove it with the command
git tag -d name-of-the-tag
to avoid pushing it back to the repo.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
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