Arran Schlosberg c6c85589af feat: signed commit when renaming upstream module (#61) ... ## Why this should be merged Signs commits for auto-renaming the Go module, originally introduced in #51 with unsigned commits that can't be merged to `main`. ## How this works Changes the commit action to use [`ghcommit`](https://github.com/planetscale/ghcommit), which was made specifically to allow for keyless signing (GitHub signs the commit). The workflow no longer opens a PR to the `renamed-go-module` branch as it's redundant and the generated branch can be used directly. The commit message includes the `workflow_dispatch` trigger branch as well as a hash of the workflow file for a complete audit trail. I removed the commented-out PR trigger as it's unnecessary. In development we can now just trigger the workflow on the dev branch. ## How this was tested Inspecting [the commit](572b8ab74e) generated by a [workflow run](https://github.com/ava-labs/libevm/actions/runs/11357025696/job/31589219847). It is identical in modifications to the one reviewed in #59.		2024-10-17 12:47:06 +11:00
..
go.yml	chore: cleanup after repo and default-branch renames (#55)	2024-10-11 10:29:32 -07:00
golangci-lint.yml	chore: cleanup after repo and default-branch renames (#55)	2024-10-11 10:29:32 -07:00
libevm-delta.yml	chore: cleanup after repo and default-branch renames (#55)	2024-10-11 10:29:32 -07:00
rename-module.yml	feat: signed commit when renaming upstream module (#61)	2024-10-17 12:47:06 +11:00