Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
John Garcia
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 03, 2015

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?

I dont understand it. Branch-Restrictions with wildcards work without problems, tag restrictions dont?

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
AUG Leaders

Atlassian Community Events