Implicit tagging happening on an old commit and the tag name is same as the branch name

[Ankit Gupta]

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.

[Theodora Boudale]

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

git tag

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.

Kind regards,
Theodora