I would like my team to be allowed to create repositories on their own, but I can't trust that they will configure the branch management of the repository properly. Is there a way to ensure that the same branch management rules are applied to all team repositories new and existing?
There are certain aspects that can be enforced, such as limiting access by group for example. Beyond that, you can prevent branch (bookmark) deletion as well as prevent history re-writes but I believe that is the extent.
More details here:
Original feature request with comments/info here:
Hope this helps!
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