chore: drop the exclude entries for the retired mutation/fuzzing workflows - #104
Merged
Conversation
…flows rhiza v1.5.0 retired `.github/workflows/rhiza_fuzzing.yml` (#1568) and `.github/workflows/rhiza_mutation.yml` (#1572), and stopped offering mutation testing in the ecosystem at all (#1492). No bundle under `bundles/` ships either path now, so these entries decline a file the sync can no longer deliver — they describe a gate that no longer exists on either side. Nothing about CI changes: neither workflow is synced with or without the entries. Any copy still sitting in `.github/workflows/` stays there, because the orphan sweep only considers paths recorded in `template.lock`'s `files:` list and these are absent from it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repo’s Rhiza template configuration to remove now-obsolete exclusions for retired mutation/fuzzing workflows, aligning the config with Rhiza v1.5.0’s current delivered workflow set.
Changes:
- Removed the
exclude:entries for.github/workflows/rhiza_fuzzing.ymland.github/workflows/rhiza_mutation.yml. - Removed the explanatory comment blocks that justified excluding those retired workflows.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
18
to
22
| exclude: | ||
| # The template's LICENSE. `legal` is synced for SECURITY.md and the community docs, | ||
| # but the licence text is this repository's own: the bundle ships MIT under | ||
| # "Copyright (c) 2025 Jebel Quant Research", which is not this repo's holder. | ||
| - LICENSE |
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.
rhiza v1.5.0 retired
.github/workflows/rhiza_fuzzing.yml(#1568) and.github/workflows/rhiza_mutation.yml(#1572), and stopped offering mutation testing in the ecosystem at all (#1492). Nothing underbundles/ships either path now, so excluding them declines a file the sync can no longer deliver.This drops the two entries and the comment paragraphs that existed only to justify them. Where a comment also explained why the other workflow was deliberately left in the sync, that note goes too — it describes a live gate that no longer exists.
No CI behaviour changes. Neither workflow is delivered with or without these entries.
This does not delete any leftover workflow file. Orphan cleanup only considers paths recorded in
.rhiza/template.lock'sfiles:list, and these are absent from it, so a copy still present in.github/workflows/stays put either way. That is a separate cleanup.🤖 Generated with Claude Code