[mixmastamyk]

Maybe but one important reason to have it done externally is to confirm it works elsewhere.

[TylerE]

One bug that's bitten me a time or two is the rather annoying case-preserving but not case-sensitive MacOS filesystem. This can mean a link works locally, but not when e.g. deployed to a linux server.

[Jackevansevo]

It's a valid reason to have stuff run in CI (i.e. consistent environment). But for my line of work I can't think of a single scenario where the architecture / platform has ever caused issues in tests, typically it's caught at build time / when resolving dependencies/packages.

[mixmastamyk]

Forgetting to commit a file is pretty common. Non-existent folder, not updating out-of-tree config, etc.

[nextlevelwizard]

Have easy way to run your tests in container. Then you don’t need to worry, unless you are deploying on strange hardware