We are evalulating the plugin "Force Field" version 1.2.1 on Bitbucket Server 3.11.2.
I configured the hook for a test repository and enabled it. Under "Reject Force Push to Branch" I set the value of
Hook did not blocked the force push. Did I do something wrong?
Could you please guide? Thanks.
If you are using Bitbucket Server 3.10 or higher, Bitbucket Server's built-in branch permissions will let you do the equivalent of the "Force Field" hook.
You can set up a permission on the branch and tick the "Prevent rewriting history" checkbox.
Note that this will only reject commits that actually rewrite the history. Doing a git push --force on a branch that can be fast forwarded will not be rejected. (As in that case the --force option is redundant)
It will also prevent pushing rebases of the branch.
I hope this helps,
Haven't used Force field plugin yet, but stash comes with a Reject Force Push , if you enable that it works fine for sure. Only difference is you cant select the branches that you want this to be applied to. Other work around would be to use the branch permissions in stash to prevent push to master(again that is push to master in general and not push --force)
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