We currently run Stash 2.3, and have a group called 'mergers' that is used to permission the master branch so that only certain users can push to master. Most of the time we keep this group empty until we do a release.
When it comes to doing a merge into master, we have to add a user to the 'mergers' group, and then remove them shortly after, once the merge is done.
My question is: is there a facility built into Stash to allow pull-request merges to take place using a different group of users to the one that sets the branch permission? Or to put it another way, only allow merges into branch X (master) via pull-merge requests in the browser only?
Unfortunately we don't have anything out-of-the-box at the moment.
You might be interested in this open ticket, which you might want to vote for and watch:
It isn't actually very hard to write a hard-coded plugin that implements the RepositoryPreReceiveHook and blocks any changes to 'refs/heads/master'. That blocks only pushes, and the master branch permissions will be checked as-per normal via branch permissions in a merge.
I hope that helps.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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