> I am all in favor of having all kinds of automation to work on
> hundreds of packages in parallel, and it might be a good idea to run
> the Salsa CI every once in a while even with no or just few changes to
> validate that there are no regressions due to changes in dependencies,
> but please limit triggering parallel Salsa CI runs to the maximum
> amount you will be able to read/debug in case there are failures.
>
> If you know you are doing a minor typofix, removing a trailing space
> etc and don't need CI at all, please pass the git option `-o ci.skip`
> when pushing.
>
> Example:
> git push -o ci.skip
I'm using the GitLab REST API through python-gitlab to automate those
commits. Do you know if there's a way to do the same thing in that case,
other that using "[skip ci]" in the commit message, which pollutes the
git history
Something tricky but should work might be, in Settings>CI/CD, update the "CI/CD configuration file" field from d/salsa-ci.yml to something invalid before doing the changes, and restoring it afterwards?
In API it would be default_ci_config_path in /application/settings.
Best regards,
Tianyu