PR got merged remotely - merge checks were skipped

[David Fanjkutić]

EDIT: ignore this question because we figured it was an error on our end - we disabled the merge check temporarily.

Bitbucket Server v7.17.4

Hi, we noticed that a PR that had conflicts got merged remotely while resolving those conflicts. That should not have happened because the PR was not yet passing the merge checks. Why is it possible to merge a PR remotely and avoid the merge checks? In our case the required number of approvals was not reached.

[Ulrich Kuhnhardt _IzymesCo_]

Thanks for posting your EDIT update. Glad you worked it out! Let us know if you need any help with your SCM process in Bitbucket!

Cheers, Ulrich

Izymes