seriesoftubes/.github/workflows
Frederic Jung 2d1f48f3e6
CI: tests in four parts on four runners, every core in use, older PR runs cancelled
npm test ran every file one after another (--test-concurrency=1, from when there were three files). It now runs as many files at once as there are cores (TEST_JOBS=1 for the old way), and --shard i/n picks one of n parts of about equal time, balanced by tests/durations.json (npm run test:timings). CI runs four parts and the build side by side; a final 'test' job is green only when all are, so the check keeps its name. A newer push to a PR cancels the older run.
2026-10-31 14:11:02 +01:00
..
auto-release.yml Release automatically when the version on main changes 2026-10-24 21:54:52 +02:00
ci.yml CI: tests in four parts on four runners, every core in use, older PR runs cancelled 2026-10-31 14:11:02 +01:00
claude.yml Answer @claude mentions on issues and PRs, including PRs from forks 2026-10-27 07:01:38 +01:00
perf-comment.yml Performance benchmark on a big network, posted on every PR 2026-10-26 06:39:23 +01:00
perf.yml Fewer merge conflicts: actions by area, one city per line, sorted dictionaries 2026-10-27 10:10:16 +01:00
release.yml Architect runs: a generated run every week 2026-10-30 13:44:04 +01:00
weekly-puzzle.yml Architect runs: a generated run every week 2026-10-30 13:44:04 +01:00