I'm +1 on this -- and going further to implement this cleanup too: https://lists.debian.org/debian-go/2024/11/msg00057.html
That would make Go packages more like all other Debian packages, while still running the "test_the_archive" job. My only adjustment of my earlier proposal is that I believe the generated debian/salsa-ci.yml file should not have the 'DO NOT MODIFY' keywords in them: we wan't to allow package maintainers to modify debian/salsa-ci.yml for any package-specific tweaks, much like for all packages using Salsa CI pipelines. /Simon Félix Sipma <fe...@debian.org> writes: > Sorry, I clicked merge instead of approve :-). > > Thanks for working on this! > > On 2024-12-21 14:36-0800, Otto Kekäläinen wrote: >>Hi! >> >>Can somebody press the "Approve" button at >>https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests/2 >>so I feel confident merging it? >> >>The current Salsa CI pipeline in go-team does not test if the Go >>package can build so having basic Salsa CI capability seems like an >>obvious thing to do, and nobody had concerns about it. Once this is >>merged, people can enable the instance runner on their packages and >>start using it so we accumulate more feedback, and can later further >>optimize the salsa-ci.yml in Go packages.
signature.asc
Description: PGP signature
