mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-06 05:17:15 +00:00
Maciej Lisiewski
d7244125e9
Thirteen guard workflows (fifteen jobs) ran on the same 4-vCPU Ubuntu runner, all started right after detect, each paying a checkout and a full billed minute for 0-13s of work: infographics, profile archives, case collisions, blob size, lazy_deps imports, stale icons, unrelated histories, contributor attribution, uv.lock, prompt-surface and package-lock diffs, the supply-chain scan and dependency bounds, and the Docker lint. repo-guards.yml runs them as steps of one job. Each step keeps its old lane gate in its `if:`, and runs whatever an earlier step did (`!cancelled()`), so one red guard never hides another; any failed step fails the job, which all-checks-pass requires. The review-status-* artifacts the live PR comment reads keep their names. Files the steps write go under $RUNNER_TEMP, and the guards that need no toolchain run before setup-pm, whose dependency phase also checks the lock. The four PR-only jobs the strict release gate tolerated as skips are now steps of a job that runs on every event, so the only tolerated release skip left is the deferred Desktop E2E.