Am 27.08.25 um 22:43 schrieb Soren Stoutner:
Yet another busywork change...
It’s not just a busywork change. If you have the CI set to `recipes/
debian.yml@salsa-ci-team/pipeline` and someone forks the package, Salsa CI
does not automatically run on the fork because this setting is reset to the
default. But, if you leave this setting as the default and create a debian/
salsa-ci.yml file, then forks automatically have the same Salsa CI as the
source repository.
That's not true, at least I can't confirm this. I moved a package into
the DPT namespace and forked the project afterwards into my namespace
the CI setting with the global pipeline is still there!
In general I disagree to the proposal Otto has made. The need to
manually add a control file is the opposite what I expect, we should
decrease the amount of work. Adding a extra files to the debian/ folder
makes it not easier to do package maintenance. The default should be
that some CI is triggered automatically without any needed action by a
maintainer.
I try to use the mentioned recipe in all Python packages and avoid to
add some extra file there I'm listed in the maintainer field.
I only add a dedicated YAML file if I'm not satisfied by the global
recipe, e.g. mostly if I've an arch related binary and building on some
architecture will always fail as the platform isn't supported.
--
Regards
Carsten
