mirror of
https://github.com/storytold/craft-common-actions.git
synced 2026-11-22 10:31:50 +01:00
With archive-command, a build (<os>) job per runner builds the tests once into a nextest archive; the shard legs download it and build nothing, and only they wait for the build job. after-archive-command runs in the build job after the upload. With cache-workspace-crates, the saving leg writes a rolling dependency entry that keeps the workspace crates, and every leg restores the newest one with restore-mtimes. The lint legs move to a lint job of their own that never waits for the build. Every job's setup is actions/gate-setup; commands run through actions/gate-run. Every new input defaults to today's behaviour. The save-condition guards read the cache-save and writes inputs every job passes to gate-setup: the build and lint jobs carry the approved condition, the gate job the same narrowed to its one saving leg per runner. Result markers are files named after their leg and download with merge-multiple, so one shard or one build lands where the check reads it. The archive upload overwrites on a re-run. archive-command without test-shards is an error. The first-party actions are pinned to the commit that added gate-setup.