mirror of
https://github.com/backnotprop/plannotator.git
synced 2026-09-14 14:17:26 +08:00
991b6e2649
b6cf7e5badded a guides-show job to test.yml and075b71dbdropped it again on the theory that the tag-time gate in guides-show-deploy.yml is enough. It is not: the committed viewer manifest pin is compiled into the release binaries independently of the viewer deploy, so a budget or manifest break has to surface on the PR that causes it, not on the release tag where the only two options are ship a stale pin or hold the release. Restored with a path gate, since the viewer build only reads apps/guides-show and the packages it bundles. HEAD is the PR merge commit, so HEAD^1 is the base tip and diffing the two is exactly the PR's changes; fetch-depth 2 is all that needs fetching, no extra action and no network call. Anything the gate cannot resolve (a push to main, a manual run, a checkout that is not the merge commit) runs the job, because skipping is the risky direction. The work itself is about 2.6s after install. guides-show-deploy.yml is unchanged.