UI Issue: Long Branch Name Overflow in Pull Request Conversation Section

[ranathedev]

Select Topic Area

Bug

Body

Issue Description:
In the Pull Request Conversation section, when the branch name is exceptionally long, it overflows beyond its container instead of wrapping or truncating properly. This causes a UI glitch, as seen in the attached screenshot.

Steps to Reproduce:

• Create a branch with a long name (e.g., "dashboard-arrival-departure-and-stay-should-be-precise-for-the-reservations-so-the-user-can-see-who-is-arriving-stay-and-on-the-departure").
• Open a Pull Request with this branch as the source.
• Go to the Conversation section of the Pull Request.
• Observe how the branch name overflows outside the container.

Expected Behavior:

The branch name should either:

• Wrap within the container.
• Be truncated with an ellipsis (...), and show the full name on hover.

Actual Behavior:
The branch name overflows outside the container, impacting the visual appearance of the page.

Environment:
Browser: Chrome 131.0.6778.69
OS: Ubuntu 22.04
Screenshot:

Additional Notes:
This issue affects usability and the readability of branch names in the Pull Request interface. It would be great if GitHub could implement a fix for handling long branch names gracefully.

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

[shinybrightstar]

Welcome to the GitHub Community, @ranathedev , we're happy you're here! You are more likely to get a useful response if you are posting your question(s) in the applicable category and are explicit about what your project entails--giving a few more details might help someone give you a nudge in the right direction. I've gone ahead and moved it to Pull Requests for you. Good luck!

[ranathedev]

Thank you for the warm welcome and for moving my post to the Pull Requests category! It’s much appreciated. I may have overlooked the category while posting, so I apologize for the oversight. Thank you for pointing me in the right direction and for your support!