Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Merge button is always avalaible

Jessy Giacomoni May 5, 2025

Hi everyone

I have a problem, for example if I make remarks in the pull request and I uncheck the merge button and always activate,
I can merge the pull request regardless of the state of my tasks, why?

Thanks a lot,

image.png

3 answers

2 accepted

1 vote
Answer accepted
Ulrich Kuhnhardt _IzymesCo_
Atlassian Partner
May 6, 2025

Hi @Jessy Giacomoni 

I concur with @Patrik S - merge-checks can be enforced by subscribing to the Bitbucket premium plan (USD3 extra per user per month). This will give you confidence that all merge conditions are met and pass before the PR can be merged.

Depending on the size of your team, Workzone for Bitbucket cloud takes pull request workflows a few steps further based on enterprise requirements, including

* Mandatory reviewers/approvers

* Reviewer groups with approval quota per group

* file/path sensitive reviewers/groups with approval quota

* Automatic merge on approval or incoming build result

* Respecting all existing Bitbucket repository settings, as per your screenshot

* Workspace, Project and Repository level configuration

* Bitbucket premium is not needed.

[!] Give Workzone a try in your workspace, it's free for teams <= 5 users :)

 

 

0 votes
Answer accepted
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 6, 2025

Hey @Jessy Giacomoni ,

Thank you for reaching out to the Community!

By default, the merge checks are just a suggestion for the developer, meaning that the developer can still merge the changes even though not all the merge checks were met (see Suggest or require checks before a merge)

The ability to enforce that each and every merge check is satisfied before a developer has access to merge is part of the Premium plan, where you would need to enable the option "Prevent a merge with unresolved merge checks" in the branch restriction.

This would enforce that all the merge checks configured in that branch restrictions will be mandatory before the users are able to complete the merge. Even though they see the merge button, with that option enabled, they wouldn't be able to complete the merge and a warning message will be shown.

I'm sharing below the instructions to upgrade in case you decide to upgrade to Premium to use the merge check enforce feature : 

Thank you, @Jessy Giacomoni !

Patrik S

0 votes
Jessy Giacomoni May 20, 2025

Thanks for your answer! 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events