cleanup: purge defunct/orphan CI files (2026-07-08 broader)#51
Merged
Conversation
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
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.
Supersedes #50 from prior cimas-sync waves.
Summary
Broader-orphan cleanup: purge defunct / orphan CI files across the fleet. Follow-up to the 2026-07-05
generate.ymlcleanup wave that landed as part of themetanorma/ci#347remediation. This picks up the historical drift the ci#347 scope filter deliberately excluded.Files removed (all no longer in cimas.yml mapping)
.hound.yml— Hound code review service defunct since ~2020..github/workflows/rake.yml— orphan rake workflows (superseded by cimas-generated variants undermaster/rake.yml.erb)..github/workflows/notify.yml— orphan notify workflows..github/workflows/integration.yml— orphan integration workflows..github/workflows/test.yml— orphan test workflows.Your PR may touch just a subset — the wave is scoped to whichever of the above files actually exists on your repo.
Verification
The
cimas cleanup-orphan-filescommand only deletes files carrying the Cimas auto-generated header (# Auto-generated by Cimas: Do not edit it manually!), so hand-written or non-cimas-shape files are protected by construction. If your gem legitimately needs one of these files as non-cimas-managed, restore it in the same PR review.Related
generate.yml(ci#347).--flatten-stalefull auto-close of prior stalecleanup-orphans-*branches on this repo.🤖