3 ms·
Given how terrible GitHub search in files is, what I usually do is clone the repo and run ripgrep.
by sph 1y ago
Given how terrible GitHub search in files is, what I usually do is clone the repo and run ripgrep.
- eXpl0it3r 1y agoNot 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.
- nicce 1y agoIf 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-githubs-new-code-search/ https://github.blog/engineering/the-technology-behind-github...
- mrweasel 1y agoBut Github is actually pretty good at searching for something across all files in a repo.
- IshKebab 1y agoNot remotely as good as grep.app.
- qwertox 1y agoI 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.