Whilst working on updating the build-deps of packages affected by the move of tslocum/cbind (and cview) to codeberg and the renamed binary packages uploaded as a result, I have noticed the recent mass commit of d/salsa-ci-yml files by Marcos Talau (talau) into these repos (and, possibly, a few hundred others).
E.g.: https://salsa.debian.org/go-team/packages/amfora/-/tree/master/debian https://salsa.debian.org/go-team/packages/gomuks/-/tree/debian/sid/debian https://salsa.debian.org/go-team/packages/fq/-/tree/debian/sid/debian https://salsa.debian.org/go-team/packages/golang-github-containerd-nydus-snapshotter/-/tree/debian/sid/debian https://salsa.debian.org/go-team/packages/golang-github-awslabs-soci-snapshotter/-/tree/debian/sid/debian https://salsa.debian.org/go-team/packages/lf/-/tree/debian/master/debian >From the small sample of maybe half a dozen projects that I quickly checked (above), these repos: *) already have an existing d/gitlab-ci.yml file present *) already have Salsa CI configured to use this d/gitlab-ci.yml file The newly committed d/salsa-ci.yml files are therefore not providing anything of value that I can see. Is there a specific reason for this mass commit of additional CI files? Is it going to be followed by a mass update of repo settings to switch from d/gitlab-ci to d/salsa-ci config files? Cheers, Nick
