Re: How to do add-on merge requests and get a pipeline to run?

David Kastrup <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.devel
Message-ID <[email protected]>
Werner LEMBERG <[email protected]> writes:

>> 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.

That does not work for reviewing the list of changes.  It requires
reviewers to take a look at every separate commit.

> Dan does it this way here and then.

There must be something better than that.  It would probably just
require clicking a few check boxes for a project maintainer.

-- 
David Kastrup
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.