docs: Community & Support section + issue templates#16
Merged
Conversation
Stargazers and new users had no obvious place to file bugs, ask questions, or share ideas. This change closes that gap: - README "Community & Support" section pointing people at Issues, Discussions (Ideas, Q&A, Show and tell, Announcements), and PRs. - Structured Issue Form templates for bug reports and feature requests, asking for the info that's most often missing (macOS version, runtime, MCP client, config, logs). - Issue chooser config redirects open-ended Q&A and ideas to Discussions instead of cluttering the issue tracker, and disables blank issues so every report has at least minimal structure.
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
bug_report.yml— structured fields for macOS version, Node/Bun version, MCP client, config, and logs (the info that's most often missing today).feature_request.yml— problem, proposal, alternatives, context.config.yml— disables blank issues and redirects open-ended Q&A / ideas to Discussions so the issue tracker stays focused on actionable work.Why
Issues and Discussions were both enabled but the README never pointed at them, and the issue tracker had no templates — so a stargazer who hit a problem had no obvious next step. This change makes contribution paths discoverable and raises the floor on report quality.
Test plan