Merge checks comparison between Bitbucket server vs Bitbucket cloud

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

This article helps in mapping or finding equivalents for branch restriction rules from Bitbucket server to Bitbucket Cloud

Solution

As we know once the repository is migrated from Server to Cloud branch restrictions are not updated automatically and these rules have to be applied manually either via UI or using API.

Branch Restrictions On Bitbucket Server

Equivalent Branch Restriction Rule On Bitbucket Cloud

no-deletes

Allow deleting this branch

pull-request-only

Merge access via pull requests

1. Everyone with access to the repository has merge access

2. Only specific people or groups have merge access

requiredApproversMergeHook

Minimum number of approvals

incomplete-tasks-merge-check

No unresolved pull request tasks

Prevent a merge with unresolved merge checks(premium feature)

read-only

Everyone with access to the repository has write access(NONE)

requiredBuildsMergeCheck

Minimum number of successful builds for the last commit with no failed builds and no in progress builds

force-push-hook

Allow rewriting branch history

all-approvers-merge-check

Minimum number of approvals from default reviewers (Work around)

needs-work-merge-check

No changes are requested

Please note an equivalent for "all-approvers-merge-check" is currently not available on Bitbucket Cloud. This request is currently in our backlog   BCLOUD-14510 - Require approval from all reviewers.

 Instead we can use "Minimum number of approvals from default reviewers", for this option we can add required approvers as "default reviewers" so that merge check will be passed once all the default reviewers have approved.

Kind: require_default_reviewer_approvals_to_merge

APIs used on Bitbucket Cloud are different from Server. We do have a detailed documentation that provides insight on creating branch restrictions on cloud

References:

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.