Hiding the repo owner in the "..." breadcrumbs is a bad UX

[nickdichev]

Select Topic Area

Product Feedback

Body

I really dislike the behavior where the repo owner is hidden in the breadcrumbs. Also, the repo owner appears on the SSR and then gets hidden by the JS causing layout shift.

Forking is one of the main things you can do on the website -- so why would you hide the important information of WHO owns the repo you're looking at?

I often find myself wanting to look at other repos created by a user/organization, so hiding it behind a "..." is always one extra click.

I understand there needs to be a max limit to prevent overflow but the limit you guys have now seems way too low. Also, why not truncate the owner, eg "repo own... > repo name" so I can still click on the repo owner to actually do something instead of expanding a useless dropdown menu.

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