On Tue, May 25, 2021 at 5:26 AM Philippe Mathieu-Daudé <f4...@amsat.org> wrote: > > Document how forks can use different set of jobs and add > a big warning so no new configuration is added to this > file. > > Suggested-by: Daniel Berrangé <berra...@redhat.com> > Signed-off-by: Philippe Mathieu-Daudé <f4...@amsat.org> > --- > .gitlab-ci.yml | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml > index 533a7e61339..8c843e5f20e 100644 > --- a/.gitlab-ci.yml > +++ b/.gitlab-ci.yml > @@ -1,2 +1,16 @@ > +# > +# This is the GitLab CI configuration file for the mainstream QEMU > +# project: https://gitlab.com/qemu-project/qemu/-/pipelines > +# > +# !!! DO NOT ADD ANY NEW CONFIGURATION TO THIS FILE !!! > +# > +# Only documentation or comments is accepted. > +# > +# To use a different set of jobs than the mainstream QEMU project, > +# you need to use the "custom CI/CD configuration path" option in > +# your GitLab CI namespace setting and set it to option and set the > +# location of your custom .gitlab-ci.yml:
I found it a bit confusing. What do you think about the following: To use a different set of jobs than the mainstream QEMU project, you need to set the location of your custom yml file at "custom CI/CD configuration path", on your GitLab CI namespace: > +# > https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path > +# > include: > - local: '/.gitlab-ci.d/qemu-project.yml' > -- > 2.26.3 >
