Bitzu

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.

Source: https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/about-discussions

Practice questions

Single choice

Which topic is the best fit for a discussion rather than an issue?

  1. An open-ended how-do-I question from the community
  2. A reproducible crash with a stack trace
  3. A scheduled task assigned to one developer
  4. 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.

Select all that apply

Which are features of GitHub Discussions?

  1. Categories to organise topics
  2. Marking a reply as the answer in Q&A categories
  3. Requesting changes in a review
  4. Polls to gather opinions
  5. 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.

True or false

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.

Download on the App StoreGet it on Google Play

More GH-900 topics in this module