We have occasionally had issues with feature branch builds passing, being merged to develop, and then develop builds failing because the feature branch was so old it does something no longer relevant or correct.
Does BitBucket (we have the self-hosted version, v5.1.1) have a way to prevent pull requests from being merged if the feature branch is "too far behind" the target branch? I think another way of describing it is preventing merging to a target branch of the last common ancestor is X commits behind the target branch's latest commit.
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