Under the: settings > "branch permissions" section of our repo I setup permissions on the master branch so that only one user has write permissions. I also checked the boxes for "Prevent rewriting history", "Prevent branch deletion", and "Prevent changes without a pull request". The permission is setup using the branch name, not any wildcards.
Under the "hooks" section I also have "Reject Force Push" enabled.
Despite these settings any user and push to the master branch from their local copy of the repo. They can also force push and force push a previous commit (removing the latest commits).
Stash is V3.11.2 (Updated today, this issue also occurred in V3.10.2)
Any ideas as to why Stash is ignoring these settings? This is a serious issue for us.
Thanks to Ben at Atlassian Support! He was able to identify that the hooks were not executable in the stash repo.
It sounds like the pre-receive hooks in your repository are not triggering correctly. If the repository that Stash maintains on disk has been modified by hand (e.g. the contents of the .git/hooks directory have been modified) you may see issues like this.
Regardless, I'd raise a support request in the Stash project at https://support.atlassian.com and our awesome support engineers will be able to take a closer look and help you out.
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