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.
It's possible using the "Branch Permissions" feature under the repository's settings. Are you on Bitbucket Cloud or Bitbucket Server?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.