You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.