Delete .github/DISCUSSION_TEMPLATE directory - #93
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the repository’s GitHub Discussion templates so Discussions are no longer pre-structured by the q-and-a, ideas, and help-wanted forms.
Changes:
- Deleted the Q&A discussion template (
q-and-a.yml). - Deleted the ideas/RFC-style discussion template (
ideas.yml). - Deleted the help-wanted discussion template (
help-wanted.yml).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/DISCUSSION_TEMPLATE/q-and-a.yml | Removes the Q&A discussion form template. |
| .github/DISCUSSION_TEMPLATE/ideas.yml | Removes the idea proposal discussion form template. |
| .github/DISCUSSION_TEMPLATE/help-wanted.yml | Removes the help-wanted discussion form template. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
tschm
added a commit
that referenced
this pull request
Aug 19, 2026
.rhiza/template.yml excludes these three paths so no sync reinstates or deletes them, but exclusion only stops the sync touching a file -- it does not remove it. That left the two workflow callers pinned to `uses: ...@v1.3.4` for good: no future sync will bump them, so "inert and frozen" was the steady state. Deleting them sidesteps the frozen pin entirely, and the exclusions stay in place to keep them from coming back. Nothing is lost. Both workflows are opt-in stubs that skip unless a repository variable turns them on, and `gh variable list` is empty -- neither MUTATION_ENABLED nor FUZZING_ENABLED is set. Neither is a required status check in .github/rulesets/main-branch-protection.json. Re-enabling either was always two steps (set the variable, restore the caller); it stays two steps. .github/CONFIG.md goes for the same reason it was excluded: it no longer exists upstream at v1.4.2, and CLAUDE.md and the README are where this repo's contributor guidance lives. It follows .github/ISSUE_TEMPLATE and .github/DISCUSSION_TEMPLATE, removed in f98755e and #93. Also drop SECURITY.md's ClusterFuzzLite bullet. It claimed fuzz targets run on pull requests and scheduled batch runs, which was never true here: FUZZING_ENABLED is unset *and* the .clusterfuzzlite/ config the reusable workflow requires does not exist, so the job has only ever skipped. Removing the caller makes it permanently false, and a security policy overstating its own coverage is worse than one that says less. `make mutation` still runs mutmut locally -- that task belongs to rhiza-task, not to the deleted caller. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
No description provided.