Otto Kekäläinen <o...@debian.org> writes: >> Will new projects created by 'dh-make-golang create-salsa-project' get >> them enabled by default too, or does that require upgrading >> 'dh-make-golang'? > > Any existing package that is updated with pkg-go-tools will get Salsa > CI because of > https://salsa.debian.org/go-team/infra/pkg-go-tools/-/commit/da61572b858250c1da6a00852455149cbc5b7a10
I don't know what that is, when and how is that used? I'd like to get pipelines on my Go packages soon, since I now create forks of all Go packages I work on in my own personal workspace on Salsa just to be able to get the Salsa CI pipeline. So I'm curious how to adopt your changes into my packages. > Any new package in a future version of dh-make-golang will get Salsa > CI because of > https://github.com/Debian/dh-make-golang/commit/cdc1ff44fe856edad7767827166e03c91b716636 So I assume the answer to my question is then really 'no'? Which means you may need to re-run your batch script to enable shared runners for all Go projects a couple of times more in the future. For projects that are created with older tool versions. Can you show how to do it, if it is simple? We can all help on that. /Simon
signature.asc
Description: PGP signature
