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 @James 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?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot