On Wed, Aug 27, 2025 at 01:43:37PM -0700, Soren Stoutner wrote:
>I suggest a better practice would be to have as the CI/CD >configuration simply `debian/salsa-ci.yml` instead, 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.
Frankly, I don't imagine somebody forking my DPT repos. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature