GH-900 ยท Collaboration tools
When should you use GitHub Discussions instead of issues?
When to use Discussions instead of issues: open-ended Q&A, ideas, announcements, categories and marking answers.
Key points
- Discussions suit open-ended conversation: questions, ideas, polls and announcements.
- They are organised in categories, and in question-and-answer categories one reply can be marked as the answer.
- Issues fit specific, trackable work such as a bug or task.
Practice questions
Which topic is the best fit for a discussion rather than an issue?
- An open-ended how-do-I question from the community
- A reproducible crash with a stack trace
- A scheduled task assigned to one developer
- A change that must be reviewed and merged
Show answer
Answer: A. An open-ended how-do-I question from the community
Open-ended questions suit Discussions. Bugs and assigned tasks are issues, and reviewed changes are pull requests.
Which are features of GitHub Discussions?
- Categories to organise topics
- Marking a reply as the answer in Q&A categories
- Requesting changes in a review
- Polls to gather opinions
- Choosing a squash merge strategy
Show answer
Answer: A. Categories to organise topics, B. Marking a reply as the answer in Q&A categories, D. Polls to gather opinions
Categories, marked answers and polls belong to Discussions. Reviews and merge strategies belong to pull requests.
You can mark a reply as the answer in every discussion category.
Show answer
Answer: False
False. Marking an answer is available in question-and-answer categories.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
