nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we automate the sync and is there something that changed in the merging rules?

Ian Dorion

Greetings.

We have recently notice some changes in Bitbucket behaviour.

1. Merging rules that was working before are no longer working, for instance we have been able to merge some PR when the requirements have not been met. Requirements like 2 approvals minimum, no request changes present are no longer applied and we have been able to merge. We are investigating on our side how this happened.

2. Is there a way to prevent a merge if the repo is not synchronized with the destination branch. Or even better, could we automate the synchronization when we merge? We have notice that it was easy to overlook the sync status and commit a regression when we merge a branch that is not synchronized.

Thank you!

Accepted answers

Ian Dorion

For no.2. I have found that we can use the pipeline to sync the branches on a merge.

Still investigating on the no.1

We are also wondering if the CodeOwners plugin might interfere with the default set of rules?

All comments

Ian Dorion

Ben

Hi @Ian Dorion

The Pull Request UI has changed recently so this may be why it appears to be behaving differently:

Previously, the merge button would display as grey if not all merge checks had passed - this was regardless of whether or not merge checks were enforced (if not enforced, you could still perform the merge despite the button showing grey)
Now, the merge button displays as blue if the PR is able to be merged. So if merge checks haven't passed, but they're not enforced - you can still theoretically merge the PR. Even with this change, a dialogue box displays before the merge is completed informing the user that checks have not passed.

The only way to prevent merges from occurring when checks have not passed is to enforce the merge checks however this requires a plan upgrade as it is a Premium feature.

Hope this helps, please let me know if I have misunderstood your query.

Cheers!

- Ben (Bitbucket Cloud Support)

Ian Dorion

Thanks @Ben!

Ben

Not a problem @Ian Dorion - welcome to the Bitbucket Cloud community!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud