Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,833
Community Members
 
Community Events
168
Community Groups

Is it possible to restrict pushing Git tags to certain users in a Bitbucket repo?

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?

4 answers

1 accepted

1 vote
Answer accepted

We do not offer this feature now, but we're always accepting Proposals at bitbucket.org/site/master.

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.

I get the same.

Is there any update to this?

For what it's worth, it appears that this is now possible. According to this documentation

Using branch permissions, add the following branch permission pattern:

refs/tags/*

Restrict it to an admin account so that no other users can push tags.

p.s. @John Garcia my first attempt at posting this comment resulted in JavaScript console errors; I think because it contained HTML from copying from the documentation page. Something I didn't realize until posting a partial comment so I could get the full comment in via editing (on the dedicated edit page) which then finally surfaced the error message. Bug on your end? See below.

 

2019-11-01_16-57-53.png

Thanks @John Garcia [Atlassian]. I've raised it.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,499 views 3 10
Read article

Atlassian Community Events