ci: retire the gates the standards' reusable workflows superseded #71

2026-10-09T15:39:52Z

KofTwentyTwo commented

2026-10-09 15:39:52 +00:00

(Migrated from github.com)

What

Removes dependency-review.yml (superseded by pr / dependency-review) and renames the CI workflow and jobs to the standard contexts ci / build-test, ci / format, ci / ui-tests.

Why

K22-CI-01: the protect-main ruleset must require the standard contexts. Follow-up to #68; relates to #63 and #66.

Draft on purpose. Merge order (maintainer, #66): (1) edit the protect-main ruleset so it no longer requires Build and test (x64), Format (style gate), Dependency review (keep the pr / *, security / *, codeql / * contexts); (2) mark this PR ready and merge it; (3) add ci / build-test and ci / format to the ruleset. Doing it in another order leaves a required check that never reports.

How it was tested

YAML parses; actionlint clean; no job body changed, only names.

Checklist

Commits are signed and signed off (git commit -S -s)
Zero build warnings; format and lint are clean
Tests added or updated; the coverage gate still passes (no code changed)
Docs updated for user-visible changes (RELEASING.md names the workflow)
No secrets, credentials, or personal data
New dependencies are justified below, or none were added
Substantial AI assistance is noted: authored with Claude Code

🤖 Generated with Claude Code

## What Removes `dependency-review.yml` (superseded by `pr / dependency-review`) and renames the CI workflow and jobs to the standard contexts `ci / build-test`, `ci / format`, `ci / ui-tests`. ## Why K22-CI-01: the `protect-main` ruleset must require the standard contexts. Follow-up to #68; relates to #63 and #66. **Draft on purpose.** Merge order (maintainer, #66): (1) edit the `protect-main` ruleset so it no longer requires `Build and test (x64)`, `Format (style gate)`, `Dependency review` (keep the `pr / *`, `security / *`, `codeql / *` contexts); (2) mark this PR ready and merge it; (3) add `ci / build-test` and `ci / format` to the ruleset. Doing it in another order leaves a required check that never reports. ## How it was tested YAML parses; `actionlint` clean; no job body changed, only names. ## Checklist - [x] Commits are signed and signed off (`git commit -S -s`) - [x] Zero build warnings; format and lint are clean - [x] Tests added or updated; the coverage gate still passes (no code changed) - [x] Docs updated for user-visible changes (RELEASING.md names the workflow) - [x] No secrets, credentials, or personal data - [x] New dependencies are justified below, or none were added - [x] Substantial AI assistance is noted: authored with Claude Code 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#71