Feature Request: Filter Search Results by File Type in Code Search

[ANcpLua]

Select Topic Area

Product Feedback

Body

Hi. I’ve been using the new Code Search & Navigation tool, and it's a great improvement! One thing that could further enhance the experience is the ability to filter search results by file type. For example, if I’m debugging a large codebase, being able to filter searches to only return *.js files would be incredibly useful. Additionally, I think integrating this feature with a global search history would allow users to quickly access frequently used queries. Anyone else feel this would be useful?

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

[ANcpLua]

thanks

[ANcpLua]

ok

[look]

@ANcpLua this is supported. There are a couple of different ways.

First, you can use the language: qualifier to restrict your search to a language. For example, repo:my/repo language:JavaScript.

Second, you can use the path: qualifier to restrict to file extensions. For example, repo:my/repo path:*.html.erb. This qualifier supports globs (as shown) and regular expressions.

For more details, please review the code search syntax documentation.

[Shaileshjadav2732]

File Type Filtering:
When working on large codebases, it would be incredibly helpful to filter search results by file type. For instance, being able to search only within *.js files when debugging JavaScript code would save a lot of time and effort.

Global Search History:
Integrating a global search history feature would allow users to quickly access and reuse frequently used queries. This would be particularly valuable for developers who work on multiple projects or revisit similar issues across different codebases.

[look]

File Type Filtering: When working on large codebases, it would be incredibly helpful to filter search results by file type. For instance, being able to search only within *.js files when debugging JavaScript code would save a lot of time and effort.

You can add language:JavaScript or path:*.js to your search query accomplish this. Let me know if that doesn't meet your use case.

Global Search History: Integrating a global search history feature would allow users to quickly access and reuse frequently used queries. This would be particularly valuable for developers who work on multiple projects or revisit similar issues across different codebases.

Thanks for the suggestion. Some query history is saved (click on the search bar to expand it to see the suggestions) but I don't think this is persisted across browsers. Additionally, if there's a search you use often, you can save it by clicking the "Save" button on the search results page.