A brief history of code search at GitHub
github.blog
A brief history of code search at GitHub
1–10 of 23 posts
Re: A brief history of code search at GitHub
#2Re: A brief history of code search at GitHub
#3There probably aren't as many drill-down features as the new official way, but speed and simplicity of UI more than make up for it.
Re: A brief history of code search at GitHub
#4At least for me a common use case for org-wide code searches is to answer questions like "is the library x still used somewhere?"
To not have this include old potentially low-traffic repos is a very bad thing. I don't understand why they would do this for enterprise customers. Like we would pay extra to not have it be this way.
[1] https://github.blog/changelog/2020-12-17-changes-to-code-sea...
Re: A brief history of code search at GitHub
#5Re: A brief history of code search at GitHub
#6Was it always necessary to log in to use this feature?
Re: A brief history of code search at GitHub
#7I still think the changes made to only index repos that had activity during the last year [1] was the wrong call, and potentially makes code search dangerous for those that do not understand this. At least for me a common use case for org-wide code searches is to answer questions like "is the library x still used somewhere?" To not have this include old potentially low-traffic repos is a very bad thing. I don't under…
Re: A brief history of code search at GitHub
#8I still think the changes made to only index repos that had activity during the last year [1] was the wrong call, and potentially makes code search dangerous for those that do not understand this. At least for me a common use case for org-wide code searches is to answer questions like "is the library x still used somewhere?" To not have this include old potentially low-traffic repos is a very bad thing. I don't under…
Re: A brief history of code search at GitHub
#9I still think the changes made to only index repos that had activity during the last year [1] was the wrong call, and potentially makes code search dangerous for those that do not understand this. At least for me a common use case for org-wide code searches is to answer questions like "is the library x still used somewhere?" To not have this include old potentially low-traffic repos is a very bad thing. I don't under…
(If you have forked a long-dead project and are working on it Github support can "decouple" it from the original and then you can search it.)
Re: A brief history of code search at GitHub
#10Given that this is a "history" I can't believe they don't mention grep.app. It's pretty much the way to search entire github. There probably aren't as many drill-down features as the new official way, but speed and simplicity of UI more than make up for it.