Currently, the merge check - "Minimum number of successful builds for the last commit with no failed builds and no in-progress builds" checks the builds on the last commit of the source branch of the PR. 

However, in a situation like this - 

Two PRs are raised -

• From develop to master
• develop to feature/123
• The build triggered from develop to master fails
• The build triggered from develop to feature/123 passes

The PR from develop to master cannot be merged which is acceptable since the build failed

However, the PR from develop to feature/123 also cannot be merged because of the merge check. This is due to unrelated code on another PR. 

If there was a merge check that checked the source and destination of the triggered PR build instead of posting both builds to the commit on the source branch, it can help avoid such scenarios.