Where do you see an overview of merge checks for a pull request ?

Question

As the question says. I can't find anywhere an overview of what exactly is required for a pull request to be merged.

The only indication was this cryptic message that does't really says to much.

Also. For an user that does not have permissions to merge as per "branch permissions" setup, it will just say "bad request" (which is a bit hilarious).

And all this only when trying to merge effectively.

Am i missing something ?

Florin Iacob · Answer

Mystery solved. Bitbucket replied.

Your feedback regarded the merge checks error - simply put, the new UI is currently in A/B testing, and we haven't built the merge check list feature into the new UI yet. Sorry for the inconvenience!

If that feature is critical to you and your team, you can opt-out of the new UI A/B test by visiting http://bitbucket.org/account/admin/features/, selecting your team from the dropdown, and then disabling the "New pull request view" for now.

Thanks for your involvement  Mikael.

Mikael Sandberg · Answer

On Bitbucket Server it shows up on the right-hand side in the pull request, and the merge button is grayed out until all checks have been fulfilled. Based on what you see on Bitbucket Cloud, I suspect that you have not enabled  Prevent a merge with unresolved merge checks.

Florin Iacob · Answer

Hi Mikael,

Thanks for your response, but i think you misinterpreted my question a little bit.

I know what merge checks are. I just need to see them somewhere, before hitting the merge button.

You say that bitbucket server shows a warning sign somewhere, which you can hover and get more information. Where is that particular warning sign shown ? So i can look for it in bitbucket cloud.

I for one, would expect the following scenario to be valid:

As a bitbucket cloud (premium) user,
With merge permissions on a given pull request,
When i open a pull request overview page for a given pull request,
I expect to see visual indications on whether there are merge checks enabled for this pull request,
And be able to clearly identify the status of each merge check (num of tests required/passed, number of reviews required/passed, etc)