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

David Kastrup <[email protected]> writes:

> I'll try seeing whether I manage to come up with something workable
> for the .gitlab-ci.yml file.

I think as a first approach I will omit the "make check".  The path of a
stacked merge request is either getting merged to the parent branch (in
which case it will get reviewed and checked along with it, admittedly
begging the question why it wasn't merged into it to start with) or
being treated to additional review/countdown and merging into master
after the preceding MR got merged.

Meaning we don't need to think about changing procedures for now while
still offering a useful preview and standalone check of the second MR,
even if it does not yet get a visual comparison.

The longterm desire would likely be to have a differential visual check.
A combined check (namely using the master branch as reference) does not
make sense I think.

Without a visual check, it is clear that one does not want to speed up
the transition to "countdown" before the first MR gets merged.  But
having a tested reviewable state early is at least something.

-- 
David Kastrup