Hi @Voonyau Yong and welcome to the community.
At the moment, I'm afraid that it is not possible to separate the requirements for X successful builds and no failed builds.
If you are enforcing the merge checks, and the last commit of the source branch of the PR has a failed build, you'll need to create a new commit with successful builds only to be able to merge the PR.
We have a feature request in our issue tracker to split the "no failed builds" requirement into its own branch permission, separate from the "X successful builds":
I would suggest to add your vote in that ticket (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of new features is done as per our policy here and any updates will be posted in the feature request.
If you have any questions, please feel free to let me know.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events