This question is in reference to Atlassian Documentation: Branch permissions
We are following the git flow pattern, and we would like to enforce developpers to push to feature/* to follow the workflow. Only administrators should be able to push and merge in master and develop. How can we achieve this?
Administrators should have a "Branch permissions" item in the repo settings where you can specify all of this. It sounds like you'd just need to set permissions on "master" and "develop" so that only the administrator group (or a list of individual admins) is permitted to push or merge to those branches. Any branch not specified in the list would then be open to anyone
Thank you for your answer! But this is exactly what we configured in the branch permissions tab of our repository, and this doesn't prevent developpers from creating branches named "random" which break the git flow integration of source tree!
The idea is to prevent them from creating anything else than `feature/*` branches.
Did you ever figure this out @Maxime Rossini1 or @Jim Redmond? We have the same question. I know that I can set perms to prevent devs from writing into develop, but I want to stop anyone from being able to create a branch called 'ABC-123' off of develop...we want them to only be able to create branches like 'feature/ABC-123' but it looks like maybe this option is only available in Bitbucket Server? Can you or anyone else confirm?
@Maxime Rossini1 & @David Jackson - Thanks for your patience on getting a resolution to your issue. Atlassian has since added the 'Branching model' feature to the 'Workflow' section in Settings. The 'Branching model' allows you (and your team) to make consistent naming decisions when creating branches. See 'The Branching model' section of the 'Branching a Repository' doc for more info: https://confluence.atlassian.com/bitbucket/branching-a-repository-223217999.html
Check out the blog post that introduces the Branching model: https://bitbucket.org/blog/introducing-bitbucket-branching-model-support
Hey @Maxime Rossini1 - Thanks for your reply and feedback. You're right. I did not directly address the initial problem - "Only administrators should be able to push and merge in master and develop. How can we achieve this?" You should be able to set permissions as per the branching model (pattern) that you have set up, which allows you to restrict 'write access' and 'merging' to certain team members or teams (admins). There is an explanation of this functionality in the blog post: https://bitbucket.org/blog/introducing-bitbucket-branching-model-support. Is there a more specific solution you are looking for at the moment?
Yes I was not specific enough in my last comment. In my first answer I added a little precision: "The idea is to prevent them from creating anything else than `feature/*` branches.". So basically, branch permissions can prevent team members to push to "master" or "develop", but they won't prevent them from pushing to ANY branch other than "feature/*" or "bugfix/*".
Hi Maxime - The team shipped branching model support as noted in Collin's response above, and is working on some additional improvements for the branch types in Bitbucket Cloud.
However, we're not planning to add the functionality to 'force branch types' at this point. We see it as a valid enhancement, which would add value for many customers, so please consider creating an enhancement ticket over at https://bitbucket.org/site/master/issues adding your use case and any detail there too. We'll then be able to weigh up its priority with the other requests.
Bitbucket Cloud Product Manager
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs