From b65341fd3a28d9b7ac297ee6ec99f19fe8b8ba38 Mon Sep 17 00:00:00 2001 From: Eric Engestrom Date: Thu, 18 Apr 2024 12:32:38 +0200 Subject: [PATCH] docs/ci: explain how gitlab considers "changes" when pushing on a fork branch And add a workaround for people hitting this unexpected behaviour. Part-of: --- docs/ci/index.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/ci/index.rst b/docs/ci/index.rst index fe8c214e9ee..d173d74a3c3 100644 --- a/docs/ci/index.rst +++ b/docs/ci/index.rst @@ -305,6 +305,12 @@ The ``--target`` argument takes a regex that you can use to select the jobs names you want to run, eg. ``--target 'zink.*'`` will run all the zink jobs, leaving the other drivers' jobs free for others to use. +Note that in fork pipelines, GitLab only adds the jobs for the files that have +changed **since the last push**, so you might not get the jobs you expect. +You can work around that by adding a dummy change in a file core to what you're +working on and then making a new push with that change, and removing that change +before you create the MR. + Conformance Tests -----------------