GitHub Discussions
Discussion board in Developer tools
People recommend it as a separate place for help questions, which keeps Issues free of noise. The common caveat is that threads are hard to search and follow.
People recommend it as a separate place for help questions, which keeps Issues free of noise. The common caveat is that threads are hard to search and follow.
18 people gave an opinion
- recommend it
- 12
- criticize it
- 6
- approval share
- 67%
Recommended in 3 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 12 people recommend itNeeds 10 or more, met.
- 2 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 3 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Gives users a place for help
“The benefit is that all users who just ask for help, assistance, or are unable to install or use the software now have a place to ask.”
Comment from 2 Jan 2026 in “Why users cannot create Issues directly (Ghostty)” “Instead of trying to cram everything into Issues, why not use the underutilized Discussions tool?”
Comment from 2 Jan 2026 in “Why users cannot create Issues directly (Ghostty)” “Try asking users: open a discussion board (for example Github's Discussions)”
Comment from 3 May 2026 in “Do_not_track” Keeps Issues free of noise
“Instead of trying to cram everything into Issues, why not use the underutilized Discussions tool?”
Comment from 2 Jan 2026 in “Why users cannot create Issues directly (Ghostty)” “it's at least keeping Issues free from noise for contributors”
Comment from 2 Jan 2026 in “Why users cannot create Issues directly (Ghostty)” Useful as a filter for Issues
“seems this approach is better but still requires someone to sort through the discussions”
Comment from 2 Jan 2026 in “Why users cannot create Issues directly (Ghostty)” “Using discussions as a filter is a good idea.”
Comment from 2 Jan 2026 in “Why users cannot create Issues directly (Ghostty)”
What people said
16 of the 18 comments that mention it, newest first. Each links to the original comment.
“Discussions are useless for feedback as you cannot subscribe to just the single thread you posted”
“they each introduce vendor lock-in to varying degrees”
“It's really just a way to ignore users.”
“Try asking users: open a discussion board (for example Github's Discussions)”
“I'm on mobile, don't have access to my GitHub credentials to log in.”
“I wanted all components to run as close as possible to one another”
“discussions are kind of hidden and out of the way on GitHub”
“I don't think discussions are good. They're just the least bad right now, unfortunately.”
“The benefit is that all users who just ask for help, assistance, or are unable to install or use the software now have a place to ask.”
“seems this approach is better but still requires someone to sort through the discussions”
“it duplicates the efforts in checking for prior reports”
“Instead of trying to cram everything into Issues, why not use the underutilized Discussions tool?”
“discussions on the whole as a product are pretty bad”
“It still sucks, especially since long threads are collapsed and thus harder to ctrl-f or link a reply, but it's something.”
“it's at least keeping Issues free from noise for contributors”
“Using discussions as a filter is a good idea.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.