5 ms·
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
by aeyes 4y ago
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.
- robertlagrant 4y agoThe 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.
- dcreager 4y agoThis 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/using-files/navigating-code-on-github#cross-repository-precise-code-navigation https://docs.github.com/en/repositories/working-with-files/u... [2] https://news.ycombinator.com/item?id=34693181 https://news.ycombinator.com/item?id=34693181
- robertlagrant 4y agoThanks! That's a really fascinating search graph.