chore(ci): align main with develop — dead workflow removed, GT-622 registered - #220
Merged
Conversation
…lyses as GT-622 Every PR carries a red `CodeQL` check reading "1 configuration not found". It is not a security finding — it is orphaned bookkeeping, and the diagnosis lands on something the maturity audit already flagged this morning. `.github/workflows/ci.yml` was a live workflow with no real jobs: its only job, `Disabled`, ran `echo` on every PR and every push to `main` and `develop`. Commit 87f50ce had once given it a `codeql` job; f50030c removed that on 2026-06-06 while gutting the file. GitHub still has 82 code-scanning analyses on `refs/heads/main` under `.github/workflows/ci.yml:codeql`, the last from that same day — so the configuration is still *recorded* while nothing produces it, and every PR since has been told it is missing. 51 days. This commit does the reversible half: the file is gone. Verified first that nothing depends on it — `Disabled` is not a required check, and the only references are the CHANGELOG (historical) and the path-literal guard's synthetic fixtures, which create the name inside a temp root. The irreversible half is registered as GT-622 rather than executed. Removing the 82 analyses destroys code-scanning history on a protected branch; their historical value is nil, but that is an owner's call, not a tool's. Note that deleting the workflow does NOT clear the recorded configuration, which is exactly why the row exists. The scanning that matters is healthy and untouched: `sdk-cli-ci.yml:codeql-analysis` and `:trivy-scan` both carry 159 current analyses, and `CodeQL SAST` passes and remains required. That is the reason this is worth fixing rather than tolerating — a permanently red check trains reviewers to discount red checks, and `CodeQL SAST` shares the CodeQL name. Board: 561/622 done, 9 in progress, 48 pending, 4 deferred. Verified: 40-validate-path-literals exit 0 and its node --test suite green after the deletion, 08-validate-tracking 622 gaps / 598 EN-ES catalog sections, ci-runner governance 17/17 exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ment chore(ci): delete the dead ci.yml workflow and register GT-622
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
📊 Bilingual Coverage ImpactPR Changes
Repository Coverage
✅ Good: All EN changes have ES counterparts. Generated by GitHub Actions |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Summary
Brings
mainlevel withdevelop. The substantive work of this session already landed onmaininbcd54591(PR #217); what remains is the CI cleanup that came out of trying to merge it.Deletes
.github/workflows/ci.yml. A live workflow whose only job,Disabled, ranechoon every PR and every push tomainanddevelop. Verified before deleting that nothing depends on it:Disabledis not a required check, and the only references are the CHANGELOG (historical) and the path-literal guard's synthetic fixtures, which create that name inside a temp root.Registers GT-622. GitHub still holds 82 code-scanning analyses on
refs/heads/mainunder.github/workflows/ci.yml:codeql. That configuration was real —87f50ce3added the job,f50030cdremoved it on 2026-06-06, and the last analysis under the key is from that same day. The configuration is still recorded while nothing produces it, which is why every PR carries a redCodeQLcheck reading "1 configuration not found". Deleting the workflow does not clear the recorded configuration; removing the 82 analyses is irreversible and destroys code-scanning history on a protected branch, so it is registered as a gap rather than executed.The scanning that matters is healthy and untouched:
sdk-cli-ci.yml:codeql-analysisand:trivy-scanboth carry 159 current analyses, andCodeQL SASTpasses and remains required.Board on
develop: 561/622 done · 9 in progress · 48 pending · 4 deferred.Evolith Core Quality Gates
.mdand.es.mdfrom a single data structure, so the pair cannot drift.01-validate-docs.mjsgreen (viaci-runner governance).04-check-bilingual-parity.mjsgreen (viaci-runner governance).Verification
Everything below was green on
developbefore this PR:40-validate-path-literalsexit 0 and itsnode --testsuite green after the deletion ·08-validate-tracking622 gaps (ES 622), 598/598 EN/ES catalog sections, 543 closure records ·ci-runner.mjs governance17/17 exit 0. PR #219 merged intodevelopwith all seven required checks green and no bypass.Linked ADRs / Issues
Conventional Commits
🤖 Generated with Claude Code