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 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...
I think there’s code search companies but they are too expensive for me and I suppose some people really value it more highly.
Comically, I need the old Google search appliance and just treat it as a web source for lots of my questions (who is using log4j, etc).
(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.)
> Join the GitHub Code Search Waitlist Access is limited during the technology preview of GitHub’s future code search. Sign up today for your chance to try it and give your feedback.
You’re already on the waitlist for GitHub Code Search! We’ll email you when we’ve enabled it on your account. Make sure your primary email address is up-to-date.
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.
