Me too, but usually after I already have 15 GH tabs open and have wasted a bunch of time.

Yep I have a small shell script that caches a repo with only the last commit files and runs ripgrep on it. I'll give a go at live grep that's discusses above, that look exciting.

I’m curious to know, have you tried their dedicated search site? cs.github.com

Their default search still sucks, IMO. But the one I mentioned is comparable to Google’s internal CS.

Why do that have a good search that's not part of the main site?

I actually think cs.github.com is now the same as github.com/search. It was in beta for awhile but they recently started redirecting it.

Yeah, even after their rewrite it’s essentially worthless.

In some ways it’s even worse now, because it seems to only build an index of the repository on the first search, when I need a result now.

I usually switch the url from github.com/whatever to github.dev/whatever

That will load a web version of VS Code, and you can then use the search from there.

Yesterday I found out about git-peek (https://github.com/Jarred-Sumner/git-peek). Instead of describing how satisfying it is to use, here is a GIF: https://imgur.com/a/cT8zAha

It uses a temp directory, and deletes it when you close your editor.

I just clone it to /tmp, that gets removed on restart.

Having it as button in browser seems cool but also horribly insecure...

The button on the browser just navigates to the URL `git-peek://https://github.com/name/repo`. How your system handles this git-peek protocol is completely up to you. While the git-peek package does offer to setup a handler for this custom git-peek protocol, I went ahead and set it up manually. Now, my system calls this bash script whenever it encounters the git-peek protocol:

  #!/usr/bin/env bash
  # Expects a single argument: git-peek://<path>
  # Example: git-peek://https://github.com/Jarred-Sumner/peek
  kitty --single-instance --detach -e zsh -c "source ~/.zshrc; git peek $1"

You can set it up to do anything you like.

What happens if you click a link to git-peek://$(cat</etc/passwd) ?

I'm not sure. What?

Is there a reasonably legitimate reason to stop using this?

That's the issue here. You need to be 100% sure handler is entirely bug free or any site can redirect to that url and exploit any bug in it

I tend to clone things I'm just having a quick look around in into ~/tmp - sometimes I'm intending to spelunk through the history so I don't fancy having that much data sat on a tmpfs and "running rm -rf ~/tmp/* when I notice it's getting a bit on the large size" is minimal enough effort that it's worth it for having control over when things disappear.

I use grep.app instead, for open source projects. Many projects are indexed.

It seems great across an org now. I can quickly answer the question of is anyone using something across 1000 repos.