Issue Summary

Currently, Bitbucket Cloud's branch restriction for build status checks considers successful, failed, and in-progress builds but does not account for stopped builds. This can lead to situations where a merge is allowed even if some builds have been stopped, which may not be desirable for all users.

Steps to Reproduce

1. Set up a branch restriction in Bitbucket Cloud to require successful builds before merging.
2. Execute multiple builds on a pull request, ensuring some builds are stopped.
3. Attempt to merge the pull request.

Expected Results

The merge should be blocked if there are any stopped builds, ensuring that all builds have been completed successfully before allowing a merge.

Actual Results

The merge is allowed if there is at least one successful build, even if other builds are stopped.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available