Bug: The folder won't create if try to create it twice using "/" from the UI

[JunaidMancheri]

Select Topic Area

Bug

Body

In a repository, we can add new files. Likewise we can also add new folders, by giving "/" splitted sections.
Eg. if we want to create a file "mergeSort.js", "sorting/mergeSort.js" will create the folder "sorting" and the file inside it.

If we write "sorting" and put a "/" for the first time it will create a folder, but then if we backspace the slash, it will clear the folder and again if we tried to use the "/", it is not creating the folder this time.

Steps to reproduce:

• Try to add new file to a repo in web ui
• while adding the file, create a folder infront of it by giving "folder-name/" before the file name
• backspace the "/"
• again add the "/'
• this time the folder is not created

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

[mecodeatlas]

Welcome to the GitHub Community, @JunaidMancheri, we're happy you're here! You are more likely to get a useful response if you are posting your question 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 for you. Good luck!