Track pipelines in both source and target project for MRs
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Managing CI pipelines for MRs, particularly those created from a fork of the project.
Further details
Until gitlab-ce#23902 is implemented (if ever), there is no automatic way of running pipelines for a MR on the target project (for MRs created from a fork).
However, the MR commit exists (unreferenced) in the target project, so it is possible to manually trigger a pipeline for it, but the CI status for the MR only displays the pipeline in the source project.
Proposal
The CI status for a MR apparently looks for the latest pipeline run for the commit sha in the source project.
I propose it should search in both the target and source projects, and either take the latest pipeline or give preference to one of the projects. (This could be a setting in the target project or in the MR itself, I'm unsure which is best.)
This, by the way, corresponds to the last "better option" I mentioned in gitlab-ce#47058.
What does success look like, and how can we measure that?
What is this supposed to mean?