Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: GitHub action to rename module (#51)
## Why this should be merged Automate renaming of the Go module from `github.com/ethereum/go-ethereum` to `github.com/ava-labs/libevm`. ## How this works Before starting this PR, I branched the `renamed-go-module` branch off `master` (the upstream geth branch; our default is called `main`). It has been protected to require PRs, which are automatically generated by the workflow introduced in this PR. The new workflow is designed to be manually dispatched with an input string of the commit hash to use as a source for renaming. On dispatch, it: 1. Checks out the source commit; 2. Renames the module; 3. Makes all necessary internal changes (e.g. import renaming); 4. Runs [smoke tests](https://en.wikipedia.org/wiki/Smoke_testing_(software)); 5. Commits the changes to a new branch; and 6. Opens a PR to merge the new branch into `renamed-go-module`. ### Intended usage When performing an upstream sync to pull in new geth code, this workflow will first be run against the geth commit we intend to merge. After the generated PR is merged, the `renamed-go-module` branch will be the one incorporated into `main`. Note that the `renamed-go-module` branch requires _two_ reviewers to approve. The user who dispatches the workflow SHOULD be one, with any other valid reviewer as the other. This is because a single-reviewer workflow would allow any user to update the `renamed-go-module` branch because the PR author is `github-actions`. ## How this was tested Inspection of the generated PR #57 as well as the [workflow run that generated it](https://github.com/ava-labs/libevm/actions/runs/11298471240/job/31427495426).
- Loading branch information