Remove default reviewers for single branch and all
Asked by Ivo:

Hello,   

We need to remove the option for default reviewers from the pull requests. Currently the settings are:

**1+** approval from default reviewers  

![Screenshot from 2024-07-01 11-33-31.png](https://community.atlassian.com/t5/image/serverpage/image-id/332702i817EFB910DCD522A/image-size/large?v=v2&px=999 "Screenshot from 2024-07-01 11-33-31.png")

<br />

This option is unchecked in Repository settings --\> Workflow --\> Branch restrictions -\> 'Merge settings':   

![Screenshot from 2024-07-01 11-33-49.png](https://community.atlassian.com/t5/image/serverpage/image-id/332703i2108801BD67A2DED/image-size/large?v=v2&px=999 "Screenshot from 2024-07-01 11-33-49.png")

Is this possible?   

Regards,


Answers:
author: Patrik S
body: Hello [@Ivo](/t5/user/viewprofilepage/user-id/5517588) ,

thank you for reaching out to Community!

That particular merge check seems to be coming from a Custom Merge check configured in your repository.

Could you please navigate to **Repository Settings** \> **Custom Merge Checks** under "Workflow", and check for any existing custom merge check currently in place for that repository ?

You will likely find the corresponding custom merge check for the rule you're trying to disable, so you'd just need to turn off that merge check from that page.

I hope that helps! Let me know in case you have any questions.

Thank you, [@Ivo](/t5/user/viewprofilepage/user-id/5517588) !

Patrik S

comments: author: Ivo
body: Hello [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) ,  

Thank you very much for your response!   

I don't see any custom configuration for the repository and workspace about Cu  
stom merge checks under Repository or Workflow section.   

Repository custom merge checks:  

![Screenshot from 2024-07-02 21-46-13.png](https://community.atlassian.com/t5/image/serverpage/image-id/333099iD77D02985C8B7A76/image-size/large?v=v2&px=999 "Screenshot from 2024-07-02 21-46-13.png")  

<br />

Workspace custom merge checks:  

![Screenshot from 2024-07-02 21-48-27.png](https://community.atlassian.com/t5/image/serverpage/image-id/333100i562EB1527C491144/image-size/large?v=v2&px=999 "Screenshot from 2024-07-02 21-48-27.png")  

<br />

<br />

<br />

<br />

Regards,  
Ivo


author: Patrik S
body: Hey [@Ivo](/t5/user/viewprofilepage/user-id/5517588) ,

thanks for the confirmation.

In this case, as there are no custom merge checks, there must be some restriction in place in your repository/project that matches that pull request's destination branch.

I noticed that in your original question, you added the screenshot of one of the branch restrictions where the merge check is indeed disabled. However, could you confirm if that is the sole branch restriction in that repository?

You can have more than one branch restriction setup that applies to different branches/branch patterns, and there should be some of them that are matching with the destination branch of the pull request you used as an example.

I would suggest verifying what is the destination branch of the pull request and then confirming which of the branch restrictions in *Repository Settings \> Branch restrictions* matches with that branch, so you can turn those merge checks off for that particular branch/branch pattern.

Thank you, [@Ivo](/t5/user/viewprofilepage/user-id/5517588) !

Patrik S


author: Ivo
body: Hi [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) ,  

Thank you very much. It was restriction in another branch but now everything is fine.   

Regards,   
Ivo


author: Patrik S
body: Awesome [@Ivo](/t5/user/viewprofilepage/user-id/5517588) ! :)

Great to hear that after editing the branch restriction, everything is working.

If you ever need help in the future, feel free to reach out.

Thank you!


Tags: bitbucket-cloud

cloud