Re: Proposing 2025 workflow changes for Go team
Hi!
> I'm in full support of these changes, thank you for working on this.
Thanks!
> I think it would be a good idea to use the script at [1] to update all
> the Go team repos, after it's updated to account for the
> "%{project_path}" variable, as well as replacing
> "github.com/xanzy/go-gitlab" with its new import path.
>
> It also needs to be updated in dh-make-golang[2] and gophian[3], with
> the "%{project_path}" variable again accounted for.
I don't quite follow, what does "%{project_path}" have to do with line:
> const gitlabciymlTmpl = `# auto-generated, DO NOT MODIFY.
If you have a clear vision what to change, please file Merge Request
and assign me as reviewer, and I will dive into it and try to help you
finalize it.
> From https://lists.debian.org/debian-go/2024/11/msg00057.html
> > Change 'dh-make-golang make' to create a debian/salsa-ci.yml instead
> > of debian/gitlab-ci.yml[...]
>
> We could make the config script delete d/gitlab-ci.yml and write to
> d/salsa-ci.yml.
I have been drafting some code to do that in a WIP branch at
https://salsa.debian.org/otto/pkg-go-tools/-/commits/salsa-ci-plain,
but I am not finalizing it until the old MRs get reviews/approvals:
https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests
One step at a time.. I am trying to do everything so that the git HEAD
can be rolled out at any time and changes can be gradual and potential
surprising regressions easier to catch.
Reply to: