GitHub has a new Discussions feature, which you can see in action here. I’m trying to figure out whether to use Discourse for my software development community or go with the GitHub feature. Has anyone evaluated the differences?
AI-generated summary
The discussion compares GitHub’s new Discussions feature with Discourse for community management. dabrahams seeks input on which platform to choose. lucasbasquerotto praises GitHub Discussions for simplifying support ticket creation within the repo ecosystem, noting users are already logged in and don’t need extra accounts. However, they emphasize Discourse’s superior feature set: themes, plugins, advanced search, moderator controls, trust levels, topic timelines, bookmarks with reminders, and customizable notifications — such as being alerted to new posts in specific categories like announcements or releases. They also criticize GitHub Discussions’ threaded format for making it hard to track new posts, as notifications may not lead to the correct thread or miss updates across multiple threads. Stranik suggests GitHub Discussions is still in early development, pointing to features like marking solved answers — possibly hinting at a future Q&A focus similar to Stack Overflow. They speculate GitHub may aim to reduce comment noise rather than build a full forum. Overall, GitHub Discussions is seen as convenient for lightweight, repo-integrated support, while Discourse is recommended for richer, community-driven forums.
I liked the new Github discussions because sometimes the issue tracker is not focused in support, and some teams says to open a discussion ticket somewhere else (that might require a new account, and may be difficult to track if the support ticket is just an email).
The discussion make it an ideal place for discussions about the repository, especially support (after all, if you would create an issue, you would be already logged in Github, redirecting to the discussion makes the creation of support tickets trivial).
That said, it’s not as feature rich as Discourse, actually what you can do there is very limited and if what you want is a real forum I would recommend Discourse. In Discourse you can have themes, plugins, a great search mechanism, moderators have much more control over topics and posts, you also have the trust level system, timeline in topics, bookmarks with reminders, several ways to receive notifications about topics and posts (for example, I specified to receive notifications about topic creations in the category announcement, releases, and praise → comparison, that’s how I was notified and I visited this topic) and several features and customizations that you don’t have in Github Discussions.
Furthermore, it’s hard to track new posts in the discussions due to it’s threaded format (sometimes the notification doesn’t take you to the post that triggered it, or even if it leads you there, if there was more than 1 new post in different threads of the discussion, you will lose them, unless you search each thread, because they are not sequential).
I think they have just started making this functionality. If I understood correctly, then at the very bottom is the solved answer: Github Package Registry doesn't work as guided · vercel/vercel · Discussion #5016 · GitHub
Perhaps soon they will raise him to the first place. I don’t think they want to create a forum for discussion. Q&A service? Then might have to follow the path of Stack Overflow. To remove, for example, noise in the comments, why is it needed there?
It’s interesting to see what they are planning. Thank you.