Hacker News Reader

Comment by robertlagrant | Hacker News Reader

Not to diminish this excellent work, but:

1) I never want to search all repos globally. At worst I want to search all of my org's repos.

2) the search UI is a little clunky, in a way I'd need to be using it again to remember.

Between those two I think there's loads of progress to be made outside of raw search power. Of course it's nice to have that, but that's what I'm really after.

View on HN

I use global search from time to time to see how other projects use certain libraries. When the documentation of said libraries is sparse this can sometimes be a good timesaver.

The other big thing that works well is being able to jump directly into the source of an open source library from your code. That is powerful, but again, possibly doesn't need a giant ultra search. Just some clever linking.

This sounds like Cross-Repo Code Navigation [1], which we do support, though only for Python at the moment. And you're right that it does not use the same search index under the covers — OP is specifically describing the index for "search box"-style code search across a large set of repositories (org-scoped, global-scoped, me-scoped, etc). For Code Navigation, we have a _different_ set of interesting and bespoke indexers and storage formats. I've posted some links here if you want to learn more: [2]

[1] https://docs.github.com/en/repositories/working-with-files/u...

[2] https://news.ycombinator.com/item?id=34693181

Thanks! That's a really fascinating search graph.

Reply on news.ycombinator.com