The technology behind GitHub’s new code search
1–10 of 187 posts
Re: The technology behind GitHub’s new code search
#2Re: The technology behind GitHub’s new code search
#3Re: The technology behind GitHub’s new code search
#4The current search sucks ass, you can’t find anything.
I was trying to search for something in the WebKit source the other day and I had to use Sourcegraph because the GitHub search gave me zero results.
Re: The technology behind GitHub’s new code search
#5Re: The technology behind GitHub’s new code search
#6Sourcegraph should’ve accepted that offer from GitHub.
Re: The technology behind GitHub’s new code search
#7I use their new code search a lot to grok how people use certain features, or implement certain things. But I do wish there was a way to filter out forks. Sometimes I search a string and just get a bunch of forks all with the same result. For example, searching a common class in a Rails app often just shows a bunch of rails/rails forks, which is a lot of noise to sift through when you're trying to see how devs common…
Re: The technology behind GitHub’s new code search
#8Re: The technology behind GitHub’s new code search
#9I really hope they release this soon and that it’s actually good. The current search sucks ass, you can’t find anything. I was trying to search for something in the WebKit source the other day and I had to use Sourcegraph because the GitHub search gave me zero results.
Obvious disclaimer because I work on this (and I also worked on the legacy search): It is way better.
Re: The technology behind GitHub’s new code search
#10Sourcegraph should’ve accepted that offer from GitHub.