Degraded performance Customers may experience issues using Community search. Our team is investigating.
I am trying to write a plugin that will validate all git changes that are done to stash. I am 90% there, but the 10% could kill my whole plugin.
I am able to validate all changes that are pushed via a pre-receive hook. That works great.
I am able to validate the merge action on all pull requests via a merge-check. That also works great.
However, a user still has the ability to delete a branch from the stash UI, or alternatively create a branch in the UI. That seems to totally bypass the above hooks. I know that I can control this via branch permissions, but I don't want to use this (since I don't always want to block users from writing or merging to these branches). I'd like to give users as much control on the repo as possible but still have these validations in place.
Is there any plugin hook that I am missing which could let me accept/reject these operations too? Alternatively, if there is a way to blanket disable those actions, that might also be acceptable.
Thanks for any help!
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