Build trust in your deployment workflow with deployment permissions
Aug 8, 2019Philip Hodder

Summary
This post introduces deployment permissions and branch protection rules to Bitbucket Cloud's workflow. It details how to configure deployment permissions to restrict production deployments to specific users (e.g., repository administrators) and how to enforce branch permissions to ensure that only reviewed and tested code can be merged into the master branch. The post provides examples of `bitbucket-pipelines.yml` configurations and screenshots of the UI for setting up these restrictions.
More from the Merge Queues trail
- Unlocking efficiency with Merge Queues in Bitbucket Cloud now GA
- Inside Atlassian’s Merge Queues: How we ship faster with fewer incidents
- Merge Queues for Bitbucket Cloud, now in open beta
- Pull request intervention for infrastructure-as-code risks with Bitbucket custom merge checks
- Expanding Custom Merge Checks to the Workspace and Project level