chore: remove discussions link from issue template config#240
Merged
Conversation
discussions is being disabled at the repo level because the project does not yet have the community Q&A volume to justify a separate channel — the existing `question` label on issues covers the same use case without splitting attention.
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.
Summary
Remove the
Question → Discussionscontact link from.github/ISSUE_TEMPLATE/config.ymlso the issue creation page no longer routes users to a Discussions tab that is being disabled at the repo level.Why
The project currently has 1 GitHub Star, 557 monthly Packagist downloads, and no organic Q&A traffic. An empty Discussions tab projects a "ghost town" signal that hurts more than it helps, and splits maintainer attention between two channels. The existing
questionlabel on issues already covers the Q&A use case at this scale.Discussions will be re-enabled if organic Q&A volume picks up (rule of thumb: ~30+ Q&A items per month, or recurring "is this a bug or expected" patterns).
Verification
composer cinot run — config.yml is consumed by GitHub UI only.Security reportcontact link continues to route to the private advisory form.Notes for reviewers
The repo-level
Discussionsfeature will be disabled out-of-band after this PR merges. The order matters: link removed first, feature off second, so users who hit the link in the window between never see a 404.