Skip to content

cleanup: purge defunct/orphan CI files (2026-07-08 broader)#51

Merged
opoudjis merged 1 commit into
mainfrom
cleanup-orphans-broader-2026-07-08
Jul 12, 2026
Merged

cleanup: purge defunct/orphan CI files (2026-07-08 broader)#51
opoudjis merged 1 commit into
mainfrom
cleanup-orphans-broader-2026-07-08

Conversation

@opoudjis

@opoudjis opoudjis commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

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.yml cleanup wave that landed as part of the metanorma/ci#347 remediation. 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 under master/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-files command 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

  • Extends the 2026-07-05 orphan cleanup wave scoped to generate.yml (ci#347).
  • --flatten-stale full auto-close of prior stale cleanup-orphans-* branches on this repo.

🤖

@opoudjis opoudjis self-assigned this Jul 7, 2026
@opoudjis opoudjis merged commit 74e6eb9 into main Jul 12, 2026
14 checks passed
@opoudjis opoudjis deleted the cleanup-orphans-broader-2026-07-08 branch July 12, 2026 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant