ci(lint): a grown warning count names the file and line that grew it

lint:warnings failed with the total and the files holding the most of the rule, which are old ones the baseline allows; the file that tipped the count was never named, so finding it meant linting by hand. When a rule grows, the ratchet now lints the files that differ from the base twice, as they are and as they were there, and lists every one holding more of the rule, line and message. The base is TREK_LINT_BASE (the CI fetches the pushed-over commit on a push and the target branch on a pull request) or origin/dev; without it the report stays as it was.
This commit is contained in:
Maurice
2026-10-18 22:46:00 +02:00
parent fca42d46d9
commit f458278e88
6 changed files with 244 additions and 14 deletions
+4 -2
View File
@@ -23,11 +23,13 @@
* ESLint comes from this workspace, so the server lints with the major its
* config was written for.
*/
import { check, lintWith } from '../../scripts/lib/eslint-warnings.mjs';
import { check, lintTextWith, lintWith } from '../../scripts/lib/eslint-warnings.mjs';
import { runCli } from '../../scripts/lib/ratchet.mjs';
import { ESLint } from 'eslint';
import { fileURLToPath } from 'node:url';
const root = fileURLToPath(new URL('..', import.meta.url));
await runCli('lint:warnings', (args) => check({ root, update: args.includes('--update'), lint: lintWith(ESLint) }));
await runCli('lint:warnings', (args) =>
check({ root, update: args.includes('--update'), lint: lintWith(ESLint), lintText: lintTextWith(ESLint) }),
);