ethereum-optimism / ethereum-optimism/optimism
Detect superchain-registry changes affecting upgrade fork tests (OPCM - Upgrade 13)
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
_TODO: clean this up_
Changes to 'superchain-registry/superchain/configs/' which affect fork tests should be detected and sent alerts to #notify-ci-failures.
[Context](https://github.com/ethereum-optimism/optimism/pull/13323/files#r1876796143)
> A job that runs every few hours and tags us in #notify-ci-failures on slack seems like a good way to account for that
> Could add a CI job to make sure superchain registry commit is up to date
Contributor guide
Research direction
Start with the superchain-registry/superchain/configs/ path and read the linked context in PR 13323. Trace how upgrade fork tests consume registry changes and locate the existing CI entry point. Done means relevant changes are detected and an alert is sent to #notify-ci-failures.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100