ethereum / ethereum/execution-specs
Github Workflow Upgrades
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 505
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 116
Description
- [ ] Add coverage of other clients for EEST (`*_cov.yaml`)
- [ ] Migrate coverage of EVMONE from lcov to codecov (`coverage.yaml` -> `evmone_cov.yaml`)
- [ ] Improve reliability of fixture releases so that builds are much more reliable (`hive.yaml`)
- [ ] Discuss unifying documentation w/ @SamWilsn @spencer-tb @Carsons-Eels @danceratopz the docs trigger on new tags, we can narrow this to specific tags (`docs_deploy.yaml`)
- [ ] We want to avoid tag pollution in EELS, so we need to have the tag that gets created for releasing new fixtures appear in EELS only temporarily to achieve release, then migrated to ethereum/tests repo, then removed. That or only do releases from the fixtures repo. (`fixtures*.yaml`)
- [ ] Add a claude job that checks the diffs between EIP updates and creates auto-prs for minor updates (`check-eip-versions.yaml`)
- [ ] Migrate bash scripts to python (`/scripts`)
WELD CI Migration Notes by @spencer-tb
Contributor guide
Research direction
Start by reviewing the checklist and the referenced workflows: *_cov.yaml, coverage.yaml, hive.yaml, docs_deploy.yaml, fixtures*.yaml, and check-eip-versions.yaml, then inspect /scripts for the Bash migration. Determine which items are still applicable and whether the documentation, fixture-release, CI, and EIP-update discussions have decisions. Done would require resolving the selected workflow migrations and validating the affected releases, checks, and scripts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, github-actions, python, yaml
- Domain
- ci-cd, devops, documentation, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100