I have a repository with both pre-receive and post-receive hooks implemented but now the developers started to use the pull request (which is great!) but clicking 'Merge' button skips the logic that is in the pre- and post-receive hooks (which is blocking the merge is some cases and activating a build in the post-receive).
How can I implement the same logic for the 'Merge' button? (or make it activates the hooks?)
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot