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.