I was wondering whether there was a way to reject force push on the master branch only.
This is so developers can work on feature branches, push, rebase & force push as necessary before a code reviewer merges into master.
I'm afraid there isn't really a way at the moment. You could certainly add your own custom plugin to do just that. Otherwise you might be interested in this feature reques, which you should vote on:
Thanks for the quick response! I guess a custom plugin might be the way to go. Do you know if the code is hosted somewhere?
I found this (https://bitbucket.org/mark0815/stash-reject-force-push-hook) but I don't think that's the one used in Stash?
I'm afraid our code is currently private, although honestly it looks almost identical to out code _plus_ it has a branch selector. That would be a good starting point, and if you just want one branch to restrict then it should probably work out of the box.
https://bitbucket.org/mark0815/stash-reject-force-push-hookwas deleted back in April. Anyone know why, or if there is a replacement? I still have a copy of it locally, will republish if needed. (Though I suspect it might be broken on Stash 3.1 ... still investigating that.)
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