Do Bitbucket Cloud merge checks block a merge or only warn?

On Bitbucket Cloud, merge checks cover approvals, successful builds, unresolved tasks, requested changes, and how far a branch is behind. On all plans they warn users. Blocking a merge when checks fail, and resetting approvals when code changes, are described as Premium features in Atlassian's documentation.

The checks available

Atlassian's support page lists these merge checks.

The page says the all plans checks warn users but do not block the merge. Blocking requires the Premium setting that prevents a merge with unresolved checks.

Why the warning only mode matters

A warning is a soft control. A busy team under deadline will click through. If your policy states that code needs two approvals and a passing build, then on a plan without blocking, the policy is a convention. For access reviews and audits, be precise: describe it as a warning unless you have confirmed blocking is enabled and tested.

Setting them up

1. You must be a workspace admin to configure custom merge checks.
2. In the repository, open More actions, then Settings.
3. Under Workflow, select Branch restrictions.
4. Select Add a branch restriction and enter a branch name or pattern, such as your default branch.
5. Add merge checks in the merge settings for the restriction or under the branch permission options.
6. Save, then open a test pull request and confirm what a failing check does.

A baseline for a production branch

• Minimum two approvals, with at least one from default reviewers.
• No changes requested and no unresolved tasks.
• At least one successful build for the last commit, and no failed builds.
• A small limit on commits behind the destination, to keep builds current.
• If you are on Premium, reset approvals on source changes, and prevent a merge with unresolved checks.
• Pair with a branch permission that sends merges through pull requests. See branch permissions.

Make the build check mean something

A build check is only as good as the build. Include dependency scanning and tests in that build, otherwise a green result says little. A status that never reports can look like no failure, so confirm that a missing build leaves the check unmet.

Try it yourself

Click through the pull request gate demo to see what a blocking decision looks like next to a warning. Ask whether your Bitbucket plan can produce the same block.

Click through it at your own pace, or open it full screen.

Quick check

Safeguard policies and gates can enforce a block on a risky dependency change in the pull request build. Try a free scan at gold.safeguard.sh/scan.

Sources

• Suggest or require checks before a merge, Atlassian
• Use branch permissions, Atlassian

Last reviewed: 19 October 2026.