Ask HN: Has GitHub Search always been broken?
Very often, I search something and there are zero results. But when I click on different sections (code, repos, etc), some results start to show up.
I think it has been like this forever and I can't remember when it worked properly. Maybe my memory is failing.
With GitHub and Microsoft investing so much in OpenAI, what's stopping them from having the best code search in the industry?
24 comments
[ 4.9 ms ] story [ 67.9 ms ] threadhttps://github.com/andrewarrow/feedback/search?q=view&type=c...
but
https://github.com/andrewarrow/feedback/search?q=views&type=...
does have results.
It's still in beta (you have to request access), but it works great for me.
Every single time I have used it in the past 5+ years, it hasn't been returning all the results I expected, and now I actively avoid it. Its advanced search filters are far too limited.
If you need to search a repo for a term, you'd be better served by cloning the repo and running ripgrep on it.
(What does OpenAI have to do with anything? Code search is not rocket science.)
The people who would notice and improve the function probably grep their code.
To be honest, I’ve never much had to use their search as much as other functions.
I’ll hit “T” if I need to search a repo. The search bar is 100% only used for navigating between repos.
Put a few pre / post screenshots in this thread https://discourse.nixos.org/t/is-github-source-code-search-b...
It's right there in Lib/asyncio for Christ's sake!