We'd like to require pull requests to update release branches, but allow anyone to create the initial branch. Is there a way to enable this?
Developers in our "developers" group create release branches using the branch naming pattern "*-release" (so, for example, "my-product-1.0.0-release"). We want to require updates to those release branches to be via approved pull requests. The problem that we're running into is the initial branch creation.
Ideally, anyone in the "developers" group could create a new release branch by branching off of master and pushing the branch. However, we can't figure out how to set that up.
Adding just the "Merge via pull request" permission for our "developers" group for "*-release" almost works, but it prohibits anyone from creating the branch. We can't create via the branches page on Bitbucket or by pushing up a release branch.
Adding the "Write access" for the "developers" group totally bypasses the pull request requirement, so that doesn't suit our needs.
We could give a few specific developers write access and make them responsible for creating these release branches, but we'd prefer not to have a bottleneck like that.
Is there any way to configure this?
