Create GitHub Discussion Categories
Create discussion categories that tell contributors where a conversation belongs and what response format to expect. Categories should separate questions, proposals and announcements clearly.
Step-by-step guide
Check access and scope
You need suitable repository or source-repository permissions to manage categories. Confirm Discussions is enabled and agree on moderator ownership.
Review conversation types
Review common conversations and existing categories.
Write category guidance
Choose a category name and a clear purpose description.
- Worked example: Use Product questions for how-to support and Ideas for proposals requiring discussion. A reproducible invitation bug should follow the issue-reporting path once enough evidence exists.
Choose a suitable format
Select the appropriate format such as open discussion or Q&A.
Explain issue-reporting boundaries
Add submission guidance and point to issue reporting where appropriate.
Test contributor filing
Move a representative conversation and test the contributor path.
Verify the result
A new contributor can choose the right category and understand what information to provide.
Common mistakes
Check the handoff edge case
Using an announcement format for open ideation changes who can start conversations. Match the format to the intended participation.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.