[Debian-salsa-ci] How to skip Salsa CI to avoid unnecessary CI runs

[Lucas Nussbaum]

Hi,

On 24/08/25 at 12:18 -0700, Otto Kekäläinen wrote:
> Hi everyone using Salsa,
> 
> [Disclaimer: Please don't view this as nagging - I am putting in
> significant effort in Debian development, and I am writing this with
> the sincere belief that I am helping Debian in doing so.]
> 
> I just noticed one developer pushed git commits to 493 different
> packages in Salsa, triggering hundreds of Salsa CI pipelines.

I think that was me (during adding debian/gbp.conf files to many
packages, during DEP-14 migration).

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

Lucas