3 ms·
I don’t understand why I would ever need to do this? If I need to replace or find something across all repos in my organisation, or god forbid, Github, then so
by Aeolun 4y ago
I don’t understand why I would ever need to do this?
If I need to replace or find something across all repos in my organisation, or god forbid, Github, then something went extremely wrong architecturally.
- quickthrower2 4y agoI have found it handy on my work repo to search code. As for searching all public repo code I am not sure I see the need unless maybe you have a super-specific error code to search for.
- tex0 4y agoLike fixing a recently discovered severe security issues affecting a large number of repositories? That would be terrible indeed. But it might happen. Good to have a powerful tool at hand in that case.
- prepend 4y agoI use the current search to answer stuff like “what projects are using GitHub actions” by searching for the action yamls and look forward to this new tool working better.
- anarazel 4y agoI e.g. often check various code search tools to see whether it's worth maintaining a backward compat layer for APIs I'm in the process of changing.
- tester756 4y agoSearching stuff in std libs/runtimes/kernel, etc?
- gravypod 4y agoIn my experience it's great for: 1. When your code is too big for your IDE's built in global search. 2. When you want to share searches with others. #2 is great for design docs. You can say "<link> shows the bug is common in API usages" or "<link> shows x% of our files do this" Edit 3. When something does go wrong. > If I need to replace or find something across all repos in my organisation, or god forbid, Github, then something went extremely wrong architecturally. If your plan B for messing something up is to not have a plan B you're going to have a bad time when plan A fails :) Unfortunately, hope is not a strategy.
- thamer 4y agoThis is very useful to see examples of how people have used APIs that are either poorly documented or not at all. Or even that are well documented, really. Going from docs to code is not always straightforward. To give you just one example, recently I've been using it to find how people have written code to interface with e-ink displays. I usually have the datasheet which lists all the commands the protocol support, but building it all into a valid startup sequence of ~20 commands to activate the display is left as an exercise for the reader. So the docs will look like this: https://www.waveshare.com/w/upload/6/6a/4.2inch-e-paper-specification.pdf https://www.waveshare.com/w/upload/6/6a/4.2inch-e-paper-spec... And what I need is a sequence like this: https://github.com/joeycastillo/The-Open-Book/blob/5c5054c58e77e1986b469545d739a40bca08a805/src/OpenBook_IL91874.cpp#L292-L383 https://github.com/joeycastillo/The-Open-Book/blob/5c5054c58...
- benced 4y agoHard disagree. A very common pattern we face is we bugfix an internal npm package and then have to roll out that change to a large subset 200 microservices that consume the package. Our goto right now is sourcegraph search to figure out what the subset is.