Hi, There are also examples of some recurring changes I am doing on packages to have salsa-ci.yml enabled and legacy filenames and CIs disabled and pointed to the standard salsa-ci.yml so that the transition is seamless:
It depends on the situation. See various scenarios and how to handle them in these examples: https://salsa.debian.org/go-team/packages/powerline-go/-/merge_requests/1 https://salsa.debian.org/go-team/packages/golang-github-yuin-gopher-lua/-/merge_requests/4 https://salsa.debian.org/go-team/packages/golang-gopkg-yaml.v3/-/merge_requests/5 https://salsa.debian.org/go-team/packages/golang-github-alicebob-miniredis/-/merge_requests/4 https://salsa.debian.org/go-team/packages/privatebin-cli/-/merge_requests/1 Also, in my opinion all MRs should have a passing CI and be green, so if the package was also broken, I fixed it. Optimizing the CI without also making it actually pass is pointless waste of effort. The above MRs shows examples of how small changes usually are enough to make the CI green and thus the pipeline useful, with working email alerts and such. On Tue, 15 Sept 2026 at 13:47, Otto Kekäläinen <[email protected]> wrote: > > Hi, > > I've noticed lately that when I maintain Go packages and repeat the > same maintenance commits on almost all of them. I thought I would > share them here in case others want to re-use the patterns for these > changes (and their documentation in git commits)... > > Update Debian copyright for 2026 > https://salsa.debian.org/go-team/packages/usql/-/commit/2819e0d1.patch > > Drop redundant `Priority: optional` > https://salsa.debian.org/go-team/packages/usql/-/commit/415e8d65.patch > > Bump Debian Policy version to 4.7.3 > https://salsa.debian.org/go-team/packages/usql/-/commit/5c28181c.patch > > Bump Debhelper version from 13 to 14 > https://salsa.debian.org/go-team/packages/tiup/-/commit/04bbc8d9.patch > https://salsa.debian.org/go-team/packages/ntfy/-/commit/d9d527c6.patch > https://salsa.debian.org/go-team/packages/glow/-/commit/ec5e5cf0.patch > > Salsa CI: Start using standard filename salsa-ci.yml > https://salsa.debian.org/go-team/packages/usql/-/commit/cb006808.patch > > Update d/watch to use uscan v5 format > https://salsa.debian.org/go-team/packages/glow/-/commit/9e2b71e6.patch > > Stop using `--builddirectory` > https://salsa.debian.org/go-team/packages/tiup/-/commit/6c49d13f.patch > https://salsa.debian.org/go-team/packages/glow/-/commit/408bdca7.patch > > Stop using `--buildsystem=golang` > https://salsa.debian.org/go-team/packages/ntfy/-/commit/1a84bec9.patch > https://salsa.debian.org/go-team/packages/glow/-/commit/dcbf0270.patch > > Make the XS-Go-Import-Path line match the go.mod contents > https://salsa.debian.org/go-team/packages/glow/-/commit/b393de49.patch > https://salsa.debian.org/go-team/packages/trufflehog/-/commit/0fceefd7d.patch > > Some of these are already done (semi-)automatically by `debcraft > improve` and I am looking into automating more of these, but some have > small variations per package and rules file and can't be fully > automated.
