4 ms·

I still regularly download gh repos just to grep them because while less bad it still somehow sucks...

• ta988 3y ago
  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.
• thunky 3y ago
  Me too, but usually after I already have 15 GH tabs open and have wasted a bunch of time.
• woadwarrior01 3y ago
  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.
  • hgsgm 3y ago
    Why do that have a good search that's not part of the main site?
    • ezekg 3y ago
      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.
• andrewmcwatters 3y ago
  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.
• el_isma 3y ago
  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.
• fortunateregard 3y ago
  Yesterday I found out about git-peek (https://github.com/Jarred-Sumner/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 https://imgur.com/a/cT8zAha It uses a temp directory, and deletes it when you close your editor.
  • ilyt 3y ago
    I just clone it to /tmp, that gets removed on restart. Having it as button in browser seems cool but also horribly insecure...
    • fortunateregard 3y ago
      The button on the browser just navigates to the URL `git-peek://https://github.com/name/repo 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.
      • progval 3y ago
        What happens if you click a link to git-peek://$(cat</etc/passwd) ?
        • fortunateregard 3y ago
          I'm not sure. What? Is there a reasonably legitimate reason to stop using this?
          • ilyt 3y ago
            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
• dimator 3y ago
  I use grep.app instead, for open source projects. Many projects are indexed.
• robryan 3y ago
  It seems great across an org now. I can quickly answer the question of is anyone using something across 1000 repos.