I've had a few instances where developers have pushed tags accidentally/in error. After this point it's really difficult to get rid of them in a big team as - once they're on the remote - they tend to keep reappearing even if they're deleted as other developers end up with them in their local repos.
It would be amazing if it was possible to restrict who had permission to push tags to a Bitbucket hosted Git repo in the first place. It feels as if it should be possible given that I guess it could be achieved in a pre-receive hook, similarly to how I imagine the branch permissions are implemented?
Can anyone advise me on this. I have tried using the above documentation. If I set branch permissions to refs/tags/* or just tags/* and make sure I don't select any users (nobody has write access) it still lets me push new tags. Does anyone else experience this?
Presumably this is because, like branches, it does not affect creating new ones, it only affects changing existing ones.
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