Proactively show downstream merge conflicts on Bitbucket UI

Suppose I have a branch intended for rel/<foo> that will also need to be forwarded to a master-aligned train. Bitbucket will warn me if a parallel change to the project by some other engineer has introduced a merge conflict on my branch, which lets me fix it proactively. That’s great.

But if the merge conflict won’t happen until my diff is forward to master, nothing in the current Bitbucket UI will show me that fact.

I could imagine a Bitbucket enhancement to proactively detect and flag the guaranteed downstream merge failures, which would let me fix the problem as early in the workflow as possible.