nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to always enforce Pull Requests instead of allowing pushing directly to a repository?

Christoffer Pet3

Hey.

I am new to Atlassian Stash, but I have been playing around for a day now.

Looking at the "Repository Pemissions" page:

https://confluence.atlassian.com/display/STASH028/Using+repository+permissions

I can read that a user with the WRITE permission can create a Pull Request, approve and merge it, but also Push directly to the repository.

It seems like users with the WRITE permission can bypass all kinds of code review by pushing directly to the branch, hence by ignoring to create Pull Requests.

Is there a way that enforce that all commits to master has to be done via Pull Requests?

Accepted answers

Christoffer Pet3

Oh I see that this question has already been asked here:

https://answers.atlassian.com/questions/152360/branch-permissions-only-allow-commits-via-pull-request

And it is not possible.

All comments

Jeff Thomas

You could setup Branch Permissions so that only certain people can write to a branch.

Christoffer Pet3

True, but I want everyone to be able to approve and merge, and I want everyone to create Pull Requests, but no one to push directly to the branch.

The problem, I think, is that the WRITE permission allows both approve+merge AND pushing directly. So if we want to enforce code review, we need to enforce Pull Requests. But with the WRITE permission you can bypass creating Pull Requests and push your commit directly to the branch, bypassing the whole code review process.

So my question still stands; Is there a way that enforce that all commits to master has to be done via Pull Requests?

Christoffer Pet3

Oh I see that this question has already been asked here:

https://answers.atlassian.com/questions/152360/branch-permissions-only-allow-commits-via-pull-request

And it is not possible.

Jeff Thomas

Sorry, I missed where you want to people to still be able to approve and merge.

You could setup a pre-receive hook by creating a plugin that prevents pushes to certain branches. See this answer for more details.

There is an open JIRA issue to do what you need without having to write a plugin, see STASH-2910.

Richard Cross

UPDATE: This functionality is now a part of Bitbucket. Under Repository Settings > Branch Permissions, you can select any branch (e.g. “master”) and then add the restriction “Prevent changes without a pull request”.

Previous Answer:

There are two 3rd party plugins that provide this missing functionality - "Pull Request Please" and "Workzone".

A JIRA was raised way back in 2012, but I don't think there's any chance of it being actioned.

unknown

Branch permissi ons now support separate permissions for writing directly to the branch vs merging via pull request.

kingdonb

This story appears to be substantially improved now: https://confluence.atlassian.com/bitbucket/suggest-or-require-checks-before-a-merge-856691474.html

You can separately grant permissions to individual branches including both "Write" and "Merge via Pull Request"

You can also "Prevent a merge with unresolved merge checks"

Nathan Jangula

This needs to be heard! I wish there was a way to resurrect this.

kingdonb

Per my reply below the fold, you can also "Prevent a merge with unresolved merge checks" which is big, too.

Phillip McKeen

Worth noting: preventing merge based on merge checks is (or was when I last checked) a premium feature.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bitbucket-server

pull-request

push