https://github.com/features/code-search
I appreciate the breakdown of how to do it yourself, but even having to signup for a waitlist to try their option when Github seems emmintely able to basically do exactly the same thing... idk. It just points to how the people that control the models really have final say here. It's hard to posit yourself as in a lucky position when you're faced up against the perfect opponent more primed to act more quickly that you are.
Symbol extraction for C and C++ is currently disabled because we were having problems with the performance of the tree-sitter queries we were using, but we are planning to bring that back.
Obvious disclaimer because I work on this (and I also worked on the legacy search): It is way better.
Yes, the new code search and navigation experience is powered by React for the frontend. We decided to use that because we wanted to build a stateful, rich navigation experience.
If you want to try it, please sign up for our beta https://github.com/features/code-search (we have been clearing the waitlist daily.)