Search scope doesn't default to repository when starting from a repo's 404

[Dschungelabenteuer]

Select Topic Area

Product Feedback

Body

Hey 👋

Because code architectures often change, it is not rare to get 404'd when trying to reach a repository's subpath (e.g. the source code of an old file that was since removed). When the 404'd URL specifically includes a path to a specific Github repo, it is pretty clear that my intent is to work with that specific repository. For example, accessing this URL returns a 404, yet is it quite safe to assume I'm looking for something in the Storybook repository.

Most repositories pages seem to default Github search's scope to repo:${pathToRepo}, which definitely makes sense. Unfortunately, repositories' 404 pages don't, which sometimes kind of break my experience when frenetically searching through codebases (sorry for spamming the search feature). Wouldn't it be better to also default Github search's scope to repo:${pathToRepo} when searching from a repository's 404 page? It almost feels like a bug!

Cheers 🤗

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