You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have branching model enabled. Let me know how to set this permission scheme:
I do not want anyone accept "administrator" group to create branches without prefixes like - "feature/", "bugfix/", "hotfix/".
I tried to set this:
- No one listed in *
- Allow write permission to everyone to write on "bugfix/*"
But this setting doesn't allow anyone to write to "bugfix/*".
The reason your branch permissions are failing is that setting "*" will trump all other settings, essentially "*" means no one can write to ANY branch as this wildcard operator will select everything.
You will need to define "bugfix/*" branch name and only add administrators with write permissions, this will mean that any branch that has "bugfix/" prefix will have these permissions applied and will only allow administrators to create these.
More information can be found here:
Hope this helps.
- Ben (Bitbucket Cloud Support)
I've just tested on my end what you want to achieve and I believe I have a solution:
Essentially what this will achieve, is that admins will be able to create any branch as they are explicitly identified to be able to do so with the "*" pattern, this pattern matches any text whatsoever.
Non-admins are not present on the "*" pattern, they can only create branches where they are explicitly defined, hence they can only create "bugfix, hotfix etc" as you have defined these.
Please create these branch permissions and test with a user, I have attached a screenshot below to show you what I mean.
- Ben (Bitbucket Cloud Support)
Yes, this is because the "*" search pattern will match all branch names and will take precedence over every other branch restriction that you define (as indicated by the yellow "!" icon next to the restriction names indicating a conflict).
Therefore as soon as Bitbucket Cloud sees that NO ONE is able to write to any branches (indicated by "*" search pattern), all the other restrictions you have defined are canceled out, and no one is able to write to any branches.
Did you manage to try out the configuration I had suggested?
- Ben (Bitbucket Cloud)
By defining "Everybody" in those other pattern types this also includes "Administrators" and creates another conflict. Are you able to define a single person in Write access for one of those branch patterns, then attempt to have them push to see if it works? The idea is that Administrator group is defined explicitly to be able to create any branch they desire, then individual user groups ie Developers are allowed write access to other pattern types (for example as shown in the screenshot which I have provided, where I have tested this and it has worked).
If this still does not work, please let me know.
-Ben (Bitbucket Cloud Support)