Bitbucket merger conditions breaking

[bagarwal]

I can see current feature broke the branch permissions.

I added few conditions for master such as:

• Minimum 2 approvals
• Minimum 1 approval from defaulter list
• No changes requested
• Reset approvals when source branch is modified

Previously it used to work but now other team mates directly getting the merge option to master (without any approvals)

[bagarwal]

Please fix this

[bagarwal]

@Patrick Wolf - Atlassian @Edmund Munday 

Can you please check this ?

[Patrick Wolf - Atlassian]

We haven't been able to reproduce this @bagarwal .  Unless the last checkbox, "Prevent a merge with unresolved checks" is selected it won't prevent the merge. The user merging will see a warning that there are unresolved checks but the merge will still happen.  Can you confirm that this box is selected?

[bagarwal]

@Patrick Wolf - Atlassian 

Correct we're seeing the warnings.

But as per my remembrance, user with write privileges can't merge the code until all the conditions for merger fulfills & then only the merge button used to display for them (ofcourse admin can do whatever he want). 

[bagarwal]

Ahh!! my bad.

Just now got what you're trying to say. So we need to enable the last checkbox i.e. Prevent the merge...

Its working as expected.

[bagarwal]

@Patrick Wolf - Atlassian 

But 1 thing, now admin also need to go through all merge conditions. Is there any way to bypass conditions for admin ???

Like users with write access need to go through merge checks but admin can bypass the merge checks (I know admin can uncheck & check again from merger settings but if there is any other way then it will be helpful)

[Eminent seo]

same issues any one help me please