Discussions should be "found" (url redirect) at org/repo/discussions

[jasonkarns]

Discussion Type

Product Feedback

Discussion Content

GitHub has a longstanding history of doing generally good things with URL structure.

Given a org/repo root, I can get issues, pulls, wiki, and even known paths to raw files within the repo.

Given that Discussions are an organization-level concept, and that the Org's discussion serves as the discussion for all repos in the organization, it would seem reasonable for {org}/{repo}/discussions to redirect to the https://github.com/orgs/{org}/discussions. That way any client can navigate to a repository's organization's discussions; just by knowing the org slug and repo name.

For more context: github already exposes the discussions at {org}/{repo}/discussions, but only for one repo. This does not make any sense if the Discussions are intended to be tied to an Organization. All repos under that organization should support the same link: {org}/{repo}/discussions and redirect to the canonical org discussions.

[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. ⭐

[jlceaser]

This is a great suggestion and makes a lot of sense from a URL
consistency perspective.

GitHub already follows this pattern in other areas — for example,
{org}/{repo}/issues and {org}/{repo}/pulls work predictably across
repos. Having {org}/{repo}/discussions behave differently depending on
whether that specific repo has Discussions enabled (vs. the org-level
Discussions) breaks the mental model.

A simple redirect from {org}/{repo}/discussions →
https://github.com/orgs/{org}/discussions for repos that don't have
repo-level Discussions enabled would:

• Maintain URL discoverability — any client or tool that constructs
  URLs programmatically could reliably reach org Discussions
• Stay consistent with GitHub's existing URL conventions
• Require minimal effort — it's just a redirect, no new UI or features
  needed

As it stands, if someone only knows the org and repo name, there's no
predictable way to navigate to the org's Discussions without already
knowing the /orgs/{org}/discussions URL pattern. That's a gap in an
otherwise well-designed URL structure.

+1 for this. Would be a small but meaningful quality-of-life
improvement, especially for tooling and automation (GitHub CLI, bots,
integrations).