Build environments unable to auto-colorize output
Currently, the runners' build environments are treated as non-interactive/not running in a terminal (which is in some sense true), but this creates issues with tools that colorize their output only when they detect standard output to be a terminal or the environment containing certain variables/values, such as the git commands, and some test suites (e.g. karma-runner, and any other suites that use the popular chalk/chalk and accompanying chalk/supports-color repos).
Please see this build for some common terminal/interactive tests, all of which return non-interactive in the runner build environment, and a demonstration of
git show being able to color when forced, but failing to do so when trying to auto-detect whether it can.
Is there any way to have the build environments convey their color support, without explicitly forcing it in the tools themselves?