CI mode can be a bit awkward to use

[abrenneke]

So because CI mode I guess isn't always on if $CI is set, I had to end up with this in my package.json, since betterer is run with all of the rest of the linting:

{
  "scripts": {
    "lint": "npm-run-all -lpc lint:*",
    "lint:betterer": "function b() { if [[ -z $CI ]]; then yarn lint:betterer:dev $@; else yarn lint:betterer:ci $@; fi }; b",
    "lint:betterer:dev": "betterer -t tsconfig.base.json --cache",
    "lint:betterer:ci": "betterer ci -t tsconfig.base.json"
  }
}    

The function is necessary so that if you do yarn lint:betterer -f some-filter, that the filter gets passed to the actual betterer command that gets run.

Maybe $CI could always run in CI mode? And ignore --cache instead of erroring that the command doesn't exist?

[phenomnomnominal]

Excuse my ignorance, where does $CI come from?

[abrenneke]

Oh, almost all CI runners out there will set a CI environment variable to something (true or 1 probably?) to indicate that you're running in the CI

[phenomnomnominal]

Oh that's super easy then, so it just comes through as process.env.CI?

[phenomnomnominal]

Is it literally just adding

if (process.env.CI) {
    return ciΔ(cwd, argv);
}

to packages/cli/src/start.ts ?

[abrenneke]

Yeah should be! (besides --cache erroring in CI mode)