nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to merge a Pull Request

t473951

Hi,

I have created a pull request which is already in approved state. When I click on Merge button, I am getting the following error.

1 out of 6 checks didn't pass, 1+ build failed

"There are not enough successful builds"

Strange thing is , we don't have any CI-CD configured for this repository. It is just a Helm charts repository configured with Argo CD.

We’ve noticed that the number of required status checks before merging a PR in our repository has increased unexpectedly. Previously, we had 3 checks, but now it's showing 6, and this is blocking our PR merges with an error like:

Is this something to do with the bitbucket issue ongoing at the moment?

Accepted answers

Nate Holland

Are you able to check your merge restrictions on your repository and workspace? It is a quirk of our product that you can enable merge restrictions around a number of passing builds without having a pipeline set up, but it is possible. So you may need to go into your repo and workspace merge restriction settings and ensure there aren't any restrictions around the number of passing builds.

All comments

Ulrich Kuhnhardt _IzymesCo_

Can you share a few more details? What does the merge-check panel look like? What are your repository's branch restrictions configurations?

t473951

Here’s the information you requested:

✅ Merge Check Panel:
It shows “6 of 7 checks passed” with a warning icon.

Also shows “1+ build passed” with another warning icon.

Error message displayed when attempting to merge:
"There are not enough successful builds"

However, there are 0 builds triggered for this PR, and we are not using Bitbucket Pipelines for this repository.

✅ Branch Restrictions Configuration:
We currently have branch restrictions enabled for the main branch.

Previously, only 3 checks were required before a merge.

(i). 2+ approvals
(ii). No changes requested
(iii) .All tasks resolved
Recently, it seems the number of required checks has increased to 6.

We have not explicitly configured build requirements or enabled pipelines for this repo.

This is a Helm charts repository, synced to Argo CD, and not tied to any CI builds.

Please help clarify:

Why is Bitbucket expecting a successful build to allow merging, when no pipelines or build integrations are configured?

Nate Holland

t473951

Thank you, Seems like My admin has added this restriction

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud