We have a Development project. Inside the project we have repositories for a number of development projects. For the most part engineers should be able to create repositories and merge code, the sort of thing that WRITE access grants. But for certain ones such as the master branch or main-line development branches within repositories we need to lock down access. The documentation on Using Branch Permissions, Controlling Access and Branch Control Patterns shows how to add additional access. Is there a way to, for instance, set branch or repository permissions to be more restrictive than what is inherited rather than less?
You can't set a repo's projects to be more restrictive than it's project's. If you need a particular repo to be more secure than the others, put it in its own project (or, more obnoxiously, set the project permissions only to those that are shared by all repos, and add individual permissions to repos as needed).
You can further restrict a branch. In fact, that's the only thing you can do to a branch, permissions-wise. Any addition of permissions to a branch will grant write access to that branch ONLY to the people listed. They will still require write access on the repo (set either at the project or repo level).
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