Consider running pipelines for merged results on Draft MRs
It is documented in https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipelines_for_merged_results/ that:
When the merge request can’t be merged, the pipeline runs against the source branch only. For example, when:
The target branch has changes that conflict with the changes in the source branch.
The merge request is a Draft merge request. I think we should still run the pipeline for merged results for Draft MRs because it is still technically mergeable and just blocked by the user temporarily.
This is also a problem because we do not run another pipeline when the MR title is changed to remove the Draft status.
We've been using pipelines for merged results in gitlab-org/gitlab for a while now and this was recently brought up and it was a very surprising behavior that many did not know about.