# GitHub Discussions Q&A category with marked answers

> Use answerable Q&A categories and marked answers so good replies stop looking like just another comment in the thread.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-discussions-q-and-a-category-with-marked-answers/
- Source: [docs.github.com](https://docs.github.com/en/graphql/reference/discussions)
- GrowthDex source hub: [GitHub Docs: Discussions GraphQL reference](/sources/github-docs-discussions-graphql-reference-docs-github-com/)
- Last checked: 2026-06-05T13:35:00Z
- Rarity: rare
- Budget: free
- Channels: GitHub, Community, SEO
- Stages: answered threads, support archive, crawlable answers, search trust


## Why this can grow

A discussion can contain the answer and still feel unresolved to the next visitor. GitHub exposes answerable discussion categories and answer-marking in its Discussions model, which means the maintainer can turn a thread into a clearer endpoint instead of a loose conversation. That makes the archive more trustworthy for searchers and lighter for support because solved questions stop reappearing as fresh work. The point is not decoration. It is making the finish line visible.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where github discussions q&a category with marked answers can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the GitHub and Community channel.
3. Use the evidence from docs.github.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

GitHub's Discussions GraphQL reference shows categories can support choosing an answer through `markDiscussionCommentAsAnswer`, and discussion comments expose viewer permissions for marking and unmarking answers.

## Adjacent tactics in the same lane

- [GitHub community profile checklist as trust audit](/growth-ideas/github-community-profile-checklist-as-trust-audit/) - 3 shared channels
- [Discourse solved schema and search priority](/growth-ideas/discourse-solved-schema-and-search-priority/) - 2 shared channels, 1 shared stage
- [GitHub releases latest link in docs and download CTA](/growth-ideas/github-releases-latest-link-in-docs-and-download-cta/) - 2 shared channels
- [GitHub profile README as operator proof surface](/growth-ideas/github-profile-readme-as-operator-proof-surface/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The community archive should answer the next visitor](/blog/the-community-archive-should-answer-the-next-visitor/) - community-led growth, SEO, documentation

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.