Given how terrible GitHub search in files is, what I usually do is clone the repo and run ripgrep.

If the repository is indexed, there isn’t really competitive search. You can find blog posts about it. They actually used ripgrep at some point. (not anymore I guess because too slow?).

Edit: ripgrep was just a test

More: https://github.blog/engineering/the-technology-behind-github...

But Github is actually pretty good at searching for something across all files in a repo.

Not remotely as good as grep.app.

I was shocked at how fast I was able to find "Open an audio file and read as mono waveform, resampling as necessary" of whisperX in audio.py on grep.app.

It was instantaneous. But where do I go from there? I cannot navigate through the code. It shows me where I can find that string, but that's it. I also cannot look at blame to see when that line got edited.

Though thanks a lot for bringing this onto my radar.

Not sure when you tried last, but it's gotten a lot better over the years. If you need something from the latest master, you'll be able to find it.

That exact exercise filled a quarter of my workday today.

I'm not being sarcastic but how do you do it on github?;) it basically never works

Not only results are incomplete but it seems once they went into training LLMs on all code they host they made sure no one else can do the same easily and so now everything is madly rate limited.

Every time I just clone and grep.