Re: How to do add-on merge requests and get a pipeline to run?
Werner LEMBERG <[email protected]>
| Newsgroups | gmane.comp.gnu.lilypond.devel |
|---|---|
| Message-ID | <[email protected]> |
> What I could do is to make the upstream branch master. MR#2 would
> consist of exactly the same commits but the runner would start.
Yes.
> But that would make the merge request garbage to review because the
> diff display would include all the dependencies of branch 3111 that
> aren't part of this merge request.
Yes. Mention this situation in the description and tell reviewers to
ignore the commits that belong to the other MR.
Dan does it this way here and then.
> One needs project maintainer role to set up CI triggers. As far as
> I can tell, the pipeline configuration is already the same as with
> normal merge requests though I don't know what that means with
> respect to the reference point for "make test-baseline". But I
> cannot trigger a pipeline.
Let's see whether somebody else has experience with such a situation.
Werner