Because of PCI 3 compliance, my management team wants us to dictate that all teams use a workflow that does not allow direct pushes to any repo and requires that all groups and projects use pull requests and code reviews to merge code into master or release branches.
Is there a way to set this universally? Or is there a way to lock settings in repositories so that only system administrators (rather than project administrators) can change them?
Stash has three 'tiers' of permissions, where you can set global, project-level or repo-level administration, read and write access to your repositories. You can also set up branch-specific permissions to prevent pushes by certain users/groups to specific branches.
It sounds like you want write-access to certain branches but only allow merges to master or release branches via pull request. We have an open feature request for this functionality, which you can vote for and watch for updates on our progress - https://jira.atlassian.com/browse/STASH-2910
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