44
The technology behind GitHub’s new code search
(github.blog)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Sep 2024
44 points (90.7% liked)
Programming
17342 readers
252 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
The new technology is: show a message saying "Whoaa! You have busted your limit!" on every search.
I didn't do a search for 6 months, but whhooaaa! Calm down with your searches!
I always found the code search more distracting than helpful. Just let me use the browser native Command + F ffs.
That doesn't really work all the time, because large files or large commits are lazy loaded on scroll, so what you're searching might not have loaded yet
The code search does a server side search
I’m usually using it not to search the codebase but to search for something specific with a file.
I think it's referring to when you're searching the entire code base(s), as opposed to individual pull requests.