<Should GitHub Discussions allow multiple accepted answers for the same question?>

[dev2401640100039-netizen]

Discussion Type

Product Feedback

Discussion Content

In many technical discussions, different answers solve different aspects of the same problem. Currently, only one answer can be marked as accepted.

Would it make sense to allow maintainers or the original author to mark multiple answers as accepted?

This could help when:

Different solutions work for different environments.
An answer becomes outdated and another provides an updated approach.
Multiple contributors provide complementary information.

Has GitHub considered this feature?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[abhitics]

I agree this would be a valuable addition to GitHub Discussions.

When writing longer discussions, feature proposals, or detailed bug reports, it's common to pause and come back later. Unlike Issues and Pull Requests, Discussions currently don't provide a way to save work in progress, which increases the risk of losing content if the browser is closed, the session expires, or the page is accidentally refreshed.

A draft feature could provide several benefits:

Allow users to save unfinished discussions and continue editing later.
Encourage more detailed and thoughtful posts without worrying about losing progress.
Improve the experience for maintainers who often prepare announcements or documentation-style discussions.
Support collaboration by allowing organization members to review a draft before it's published (if appropriate permissions are available).

Even an automatic local draft (similar to what many editors provide) would be a significant improvement, with optional cloud-synced drafts for users who work across multiple devices.

Overall, I think draft support would make GitHub Discussions much more user-friendly, especially for repositories that rely heavily on Discussions for community engagement and knowledge sharing.