> It's pretty incredible if I'm trying to find a breakage in a repo I don't understand.

> Build's failing? Easy enough:

> It's not as useful for personal projects

How often do you run into this situation, though? For your scenario to arise, you need:

(1) A repo you're unfamiliar with (which is already unusual for most people... most people spend most of their time working on repositories they've become familiar with)

(2) The unfamiliar repo to use standard build commands you already know, which is basically never the case in my experience (even cmake-based projects almost always need variables defined with custom names I don't know beforehand, and the configuration process is so onerous I find the GUI easier)

(3) An obscure enough breakage where the output is complete garbage (otherwise the compile error would just tell you the file and line, and git blame would tell you the commit directly)

(4) Knowledge that this unfamiliar repo actually would have actually built on your machine at some point (which is often not the case because cmake isn't hermetic and breakages are often due to having the wrong toolchain installed)

(5) For the problem to be a mere build error, as opposed to some running of the program that requires investing time to automate

(6) For you to not have any sort of prior CI or other form of validation on your dependencies, because you apparently didn't catch even catch a build error when it was introduced (never mind automated testing)

I could go on, but these set of circumstances are more or less indistinguishable from ~never to me.