[FEATURE] Enable GitHub Discussions for community discourse

Resolved 💬 6 comments Opened Dec 15, 2025 by PaulRBerg Closed Feb 14, 2026

Problem

Currently, all community feedback flows through GitHub Issues, mixing bug reports, clear feature requests, and more debatable/exploratory feature discussions in one place. This makes it harder to:

  • Triage actionable issues vs. open-ended discussions
  • Gauge community interest on ideas before they become formal requests
  • Have back-and-forth conversations without cluttering the issue tracker

Proposed solution

Enable GitHub Discussions for this repository. This would allow:

  • Issues for bugs and well-defined feature requests
  • Discussions for exploratory ideas, questions, showcases, and community conversations

For reference, biomejs/biome uses this approach effectively, with categories like:

  • Ideas (for feature brainstorming)
  • Q&A (for help and questions)
  • Show and Tell (for community projects)

Alternatives considered

  • Continuing with issues only, but this conflates different types of community interaction
  • External forums/Discord, but GitHub Discussions keeps everything in one place and integrates with the existing workflow

Priority

Low

Category

Other

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗