"ref may contain hidden characters" warning a bit too heavy-handed

[josh-hadley]

Select Topic Area

Bug

Body

When creating a Pull Request from a branch that contains visible but perhaps unusual characters, a warning banner that "The head ref may contain hidden characters" can appear, even when the branch name contains characters that are clearly visible.

Example from josh-hadley/branchy#1 attached:

I appreciate that GitHub might be trying to flag a potential security issue with this warning, but in this case it is simply wrong: the characters here are definitely visible. I've experienced this with other characters as well. Unicode maintains character properties that could be used to narrow this warning to flag characters that might truly be invisible. I recommend using those instead of the very wide net (non-ASCII?) that is currently being used.

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