I need to ensure that people on my team are not accidentally deleting the release tags. I tried various branch permissions and attached is one of them.
Despite setting up the branch permission, anyone on the team is able to delete the tag.
I have a similar branch permission setup for master and that seems to be working. Is the problem with the pattern I am using? If so, what is the right pattern?
In Server 5.3, we use refs/tags/v/** to prevent deletion. the second * is required.
Hi @tdacox,
This thread is about cloud Bitbucket and cloud Bitbucket does not allow consecutive wildcard usage (i.e., the second * is not allowed).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information.
Does that mean, there is no way to prevent tag deletion on Bitbucket cloud version today?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can believe that Bitbucket Cloud can't prevent tag deletion yet, Github is in front of bitbucket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.