[zegl]

The trick to make CI in large codebases fast, or how to make any system fast, is to only test what’s changed.

In CI you only need to lint the files that have changed, or run the tests that depend on code that has changed etc.

This way the time it takes to execute the tests scales with the amount of changes, and not with the total amount of code.

[DougBTX]

The difficulty with that is trust, if there’s any chance it will miss things by accident then I’d rather eat the slow runs.

Test runners that run new/changed tests first though are cool. Faster feedback on error but still comprehensive.