2 ms·
I suspect it’s largely to avoid ballooning the size of indexed search data they have to store, given the many many forks of popular repos. So a mix of biz/tech
by akerl_ 7y ago
I suspect it’s largely to avoid ballooning the size of indexed search data they have to store, given the many many forks of popular repos. So a mix of biz/tech reasons, but not really nefarious.
That said, given the nature of git, I usually just fall back to clone/grep.
- crazysim 7y agoI just have the SourceGraph extension installed. It's also usable without too. It's a bit more powerful and lets me search forked repositories too on an instance of Sourcegraph on their infrastructure. I still lament not being able to globally (like all of GitHub, not just one repo's forks) search GitHub's forks. It's amazingly useful for finding out approaches to using an API. Sorta like Google Code Search in the old days.
- sqs 7y agoSourcegraph CEO here. Yes, you can search forked repositories on Sourcegraph with regexp, exact terms, etc. Thanks for mentioning that! Here’s an example of a fork that you can search: https://sourcegraph.com/github.com/uber/gonduit https://sourcegraph.com/github.com/uber/gonduit Just change the repository owner/name in the URL to search any other one.