Hi Marcos! > During last week's DebConf I participated in a Go sprint, and one of the tasks > assigned was to add this file to several packages [1] and then adjust the CI > configuration. The first part I did was add this file; the second step I was > going to do was adjust the CI configuration. > > I apologize if this was incorrect.
Thanks for participating in the sprint and willingness to contribute to Debian! The CI setting and filename debian/salsa-ci.yml is correct. The issue is that simply activating the CI without following up on if it actually works is a purely mechanical change that anyone could do en mass in a few hours to all Go team packages. The reason this hasn't been done is mainly that such a mechanical change does not have much value. The purpose of a CI is to tell developers if a commit resulted in a testable error and thus was a regression and needs to be reverted. When CI is enabled (or modified) for a package, the person doing it should ensure that the CI passes. Otherwise the CI is moot, and a failing CI just crates extra work and confusion for the next person who wants to contribute to the package. I am happy to review your MR if you now want to follow-up on this and ensure that the actually works for e.g. these packages you modified: 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/lf/-/tree/debian/master/debian Just tag me @otto in any MR you create and I will try to review it as quickly as possible.
