ci: rename two required checks whose names describe deleted machinery (werror cache, audit cache key)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, shell
- Domain
- ci-cd, documentation, tooling
Research direction
Start with the two job definitions in ci.yml and their matching lines in .github/required-checks.txt, then check the tier table in docs/CI.md. Run tools/ci_tier_check.sh and its --live mode after renaming both checks together. Done means the ruleset is synced when the PR merges and the next PR's merge-queue run reports every required check.
Written by the indexing model from the issue text.
Description
Follow-up to the #1275 werror consolidation. It deletes tools/werror_cache_key.sh and turns the werror audit into a sub-second grep.
Problem. Two REQUIRED check names still describe the removed machinery:
werror audit ([99i], cached): nothing is cached any more;gate self-tests (section plan + audit cache key): the cache-key self-test is gone.
They were kept byte-identical in the consolidation PR on purpose. The "Protection" ruleset (17713865) is synced FROM .github/required-checks.txt only after merge, so renaming a job in the same PR creates a required check that never reports, and that blocks the merge.
Done when:
- Both jobs in
ci.ymland their lines in.github/required-checks.txtare renamed together (for examplewerror flags ([99i])andgate self-tests (changed rows)). tools/ci_tier_check.shand--livepass.- The ruleset is synced in the same session the PR merges, and the next PR's required checks all report. Verify on that PR's merge-queue run.
- docs/CI.md's tier table uses the new names.
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 102
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InauguralSystems/EigenScript
-
area:lint-tooling bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1340 ·
Maintainers usually reply within 1 day
-
area:stdlib found-by:code-review kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1338 ·
Maintainers usually reply within 1 day
-
area:lint-tooling found-by:critic kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
InauguralSystems/EigenScript#1335 ·
Maintainers usually reply within 1 day
-
area:ci found-by:critic kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#1311 ·
Maintainers usually reply within 1 day
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchetOpenarea:gates found-by:critic kind:decision
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
InauguralSystems/EigenScript#1280 · 1 comment ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/libretro-common#233 ·
-
[Bug]: chunk_span_bounds and _validated_chunk_spans reject Pydantic models ChunkSpan and AudioFileOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BasedHardware/omi#19047 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
obsproject/obs-studio#13936 · 2 comments ·
Maintainers usually reply within 1 day