Branch restrictions doesn't work for: Merge access via pull requests

[Volodymyr]

So as you can see I want to be the only one person who can do merge on master branch, but other user was able to do merge without any questions or pull requests.., just via regular commit. 

Why? Or what I'm doing wrong? Or how to restrict from merge in master ?

[Saxea _Flowie_]

Hi @Volodymyr,

You need to to select "Only specific people or groups have write access" on Write access.

[Volodymyr]

But I need all developers have write access which I added into group Developers. 

And I set only I can have a merge access, but anyway all still has it. 

Overall this access UI and confusion and awkward, hard to understand and not working.

[Volodymyr]

So again I will select the same people, me and other developer. How this will prevent and will get a linear history in the end? These specific people or everyone is the same for my case.

[Volodymyr]

So again, this is pretty obvious, everyone can write, so can commit changes, but only specific people - me, can merge. 

But this is NOT working, everyone still can merge. 

[Saxea _Flowie_]

Write still lets people merge and push to the branch. If you can write you can merge, after all, a merge is basically creating new commits.

The "Only specific people or groups have merge access" options refers to merging via pull requests.

So with your setting - only you can merge via Pull request and everyone can write/merge directly to the branch.

Typically you would restrict write access to protected branches and allow merge only via pull request to them.

[Volodymyr]

But I need like on GitHub option - Linear History!

[Saxea _Flowie_]

Bitbucket doesn't have this option built-in, however we provide an Bitbucket cloud app that add supports to creating and enforcing linear history.