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.
If I need to replace or find something across all repos in my organisation, or god forbid, Github, then something went extremely wrong architecturally.
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.
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-spec...
And what I need is a sequence like this: https://github.com/joeycastillo/The-Open-Book/blob/5c5054c58...
That would be terrible indeed. But it might happen. Good to have a powerful tool at hand in that case.
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.