Branch permissions: restrict the name of branch Edited

The Problem

In my project I want to practice a workflow in which the name of a feature branch is strict. For example, if the contributor works on issue #4, he names the branch iss4. So, let's say the desired model is:

  • Only Konstantin can push or merge into master branch.
  • Anyone can push or merge into the branch named issN (more generally, iss*)
  • No one can push or merge into the branch with the other name

What I've done

Branch permissons I've set are shown at the screenshot below:

permissions.png

What I get

  • Restriction to master works fine
  • When I tried to push a branch rubbish, I got 'pre-receive hook declined'
  • When I tried to push a branch named iss4, I got the same error, expected to get a successful push.

So, what I missed? Is it possible to get described workflow?

 

Thanks for your help,

K.

0 answers

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jun 12, 2018 in Bitbucket

Do you use any Atlassian products for your personal projects?

After spinning my wheels trying to get organized enough to write a book for National Novel Writing Month (NaNoWriMo) I took my affinity for Atlassian products from my work life and decided to tr...

23,161 views 26 12
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you