Just started to look into Bitbucket server administration and how to get restrictions to work.
I marked a branch as "Prevent changes without a pull request" to Everyone and still I can freely commit to that branch. I also limited the read access to Senior and Admin users and did the test with a regular developer account.
Is there a different way to make sure none can commit to certain branches?
Matthieu, it sounds like you are describing using the branch permissions feature of Bitbucket Server. Is that correct? Please note that none of the permissions you specify for a repository will affect a local repository; they will only be enforced once those changes are actually pushed to Bitbucket Server.
Ooo, that's a good point. I just assumed you were talking about pushing to the server. But Felix is correct, branch permissions won't (and can't) affect anyone's right to do whatever they want on their local copy of the repo. The "permission denied" error message will only be displayed when they attempt to push back to Bitbucket.
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