Jonas Hahnfeld via Discussions on LilyPond development <[email protected]> writes:
> On Sat, 2026-08-08 at 21:25 +0200, David Kastrup wrote: >> Werner LEMBERG <[email protected]> writes: >> > Maybe it is posible with some special code in the CI configuration for >> > LilyPond's git repository, I really don't know. Asking a search >> > machine didn't reveal anything that I can understand. >> >> 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. > > Just clarifying this part inline: CI triggers are maintained in the > file .gitlab-ci.yml, which can be edited by anyone. The project > settings related to CI/CD are centered around administrative tasks > such as who is allowed to cancel pipelines and jobs (Developers), > managing the list of runners, and configuring variables. Ah, I had hoped for a "somebody else's problem" scenario I'll admit. At least now I know where to actually look. This means that I could change the behavior for just my branch by pushing a commit changing its .gitlab-ci.yml file; but if the branch got merged, this would change global policies? > For the general subject I'll reply to the latest message. Thank you. -- David Kastrup
