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; } } }

Branch restriction: read/write feature branches only

rm-rf-etc

Is there not a way to restrict permissions to a group or team member, so they can only write to feature branches? Also, they should be able to push their own new feature branches, and create PR's, but not merge.

I would think this would be a common set of permissions a team leader would want but I don't see a way to get this working.

Accepted answers

Julius Davies _GitBoost_com_

It's possible using the "Branch Permissions" feature under the repository's settings. Are you on Bitbucket Cloud or Bitbucket Server?

All comments

Julius Davies _GitBoost_com_

It's possible using the "Branch Permissions" feature under the repository's settings. Are you on Bitbucket Cloud or Bitbucket Server?

rm-rf-etc

I don't know, there's no label. I open bitbucket.org, that's what I'm using.

Could you include something more specific? I'm using branch permissions, I don't see what I'm looking for. I would expect that I set read-only permission for my developers group, then add write permission for a branch pattern, but this doesn't seem possible.

jredmond

The documentation for branch permissions in BB Cloud (bitbucket.org) is at https://confluence.atlassian.com/bitbucket/branch-permissions-385912271.html .

I'm not sure exactly what you're after, but it sounds like something along these lines for the master branch:

Nobody is listed in the "write access" field (or, alternately, there's an admin user or group listed there)
"Allow rewriting branch history" is not checked
"Allow deleting branch" is not checked
The developer group (or an admin group, or a QA group, etc.) is listed in the "merge via pull request" field

That will prevent direct writes, rebases, or branch deletions on master, while still permitting people to use the PR workflow to merge their things.

You can also use a wildcard to define additional branch permissions on feature branches. However, it will be much simpler to define branch permissions on master or on a set of primary branches, and leave feature branches as they are.

Welcome!

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

Quick Links

Find more posts tagged with

bitbucket

bitbucket-cloud

permission