Cannot merge merge request due to unknown requirement
When the pipeline is not run, but merges can only be accepted after a successful run, the merge-request UI currently only states:
'Please resolve the above issues first'
However the user has no idea what issue is to be resolved (there is no text 'above').
It turns out, that if a pipeline does not run (for example no changes where triggered with the use of the changes keyword), the merge request cannot (rightfully) be merged.
However, it would be nice to let the user know that it was due to a (failed/missing) pipeline.
I suspect this is due to the fact, that before we had the 'changes' keyword, the pipeline potentially always ran, and thus, the status would be 'failed'. Now, the pipeline may not run, and so the user is no idea as to why.
I could personally resolve this issue, as I was allowed and thus could, press the 'run pipeline' button on the branch.
Having a simple text which describes the 'issue' that is to be resolved (successful pipeline run) would make this paper-cut go away.