Feature Request: Choose Branch for the "Maximum number of commits behind" Merge Check

[Matt Pedersen]

Because of our branching strategy, the "Maximum number of commits behind destination branch" merge check does not work for us. We have a branching strategy that puts us square in the BCLOUD-21964 bug. The suggestions from Atlassian have been to make sure that the source and destination branches are not behind our main branch.

If this merge check could be changed to allow us to specify the main branch instead of the destination branch, that could help us out a lot as it would force our developers to keep their feature branches up to date with the main branch.

[Theodora Boudale]

Hi Matt,

Thank you for reaching out.

I created a feature request in our issue tracker:

• https://jira.atlassian.com/browse/BCLOUD-23242

I suggest adding your vote to that feature request (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for features. You are more than welcome to leave feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Implementation of features is done as per our policy here and any updates will be posted in the feature request.

In the meantime, as already mentioned by Saxea _Flowie_, their add-on currently supports this.

Another option would be to use Forge in order to build your own app that implements a custom merge check:

• https://developer.atlassian.com/platform/forge/manifest-reference/modules/bitbucket-merge-check/

Kind regards,
Theodora

[Saxea _Flowie_]

Hi @Matt Pedersen,

Flowie, our Bitbucket Cloud addon, already supports this. You can define checks using conditions, which includes the source branch.

You can give it a try, and if you need assistance configuring it, you can contact our support.