I'd like to enforce that any development be done by branching the code, putting it through review and then performing a pull request to merge with the master branch. How exactly do I need to set this up?
It looks like the repository permissions *write* setting grants *both* the ability to merge and the ability to push. Is there any way around that? I really don't want it to be possible to push directly to master without going through a review. I'm guessing some kind of hook is necessary but I'm more of a sysadmin.
One method of achieving this workflow in Stash would be to use a gatekeeper style workflow. I gave an overview of this workflow in this question.
There is also an example hook which would stop people from pushing to one branch in a repository and only allow pull requests to be merged, you could compile and extend this example to suit your needs.
Hope that helps,
Folking workflow meets your requirements, it needs a project keeper to review/decline the writing to master, in this case, each person has its own master repo and project keeper can finally decide if the change can come into repo master, please see more: https://www.atlassian.com/git/workflows#!workflow-forking
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot