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

David Kastrup <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.devel
Organization Organization?!?
Message-ID <[email protected]>
Colin Campbell <[email protected]> writes:

> Noob and probably missing something, but is there a way to set up a
> "depends" mechanism, similar to the "closes" tag in the MR heading?
> That would seem efficient, and would mean I'm unlikely to advance a
> dependant MR prematurely.

The branch into which the MR wants to be merged is listed at its top.
If it is not main or stable/... but rather dev/..., it is a dependent
branch.  It is also listed as "2 of 2" of a "merge request stack".  You
only want to promote the 1st merge of a merge request stack to
countdown.

Does this help as first rationale?  There may be some finetuning later
in case we have visual checks and/or other outcomes of discussions, but
right now I think that those criteria are fine.  In particularly since
once the "parent" branch is merged, GitLab will reorient and reevaluate
the dependent branch on its own if I understand correctly, making it
look normal.

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