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.
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.
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
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