Although we do not support granular permissions on branches, a previously suggested approach would be to fork the repository, providing the Release Manager access to the fork.
The fork can inherit or have its own permissions. As part of the release, you could ask the manager to pull incoming changes from the parent.
This information can be found here if interested:
I hope this response was helpful.
Jason | Atlassian
The lack of "push" write access control per branch, or at least to a single ("master") branch, is causing is a lot of trouble. What are the odds of this appearing? We're trying to decide whether to endure for a while (and manually push -f back a bad commit in master every few days), or look elsewhere.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot