Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

ci(windows): gate the hook-bundle job behind the windows label

AkitaOnRailsdeb64063dd3d
diff --git a/.github/workflows/windows.yml b/.github/workflows/windows.yml
index cf2b348e..41da1507 100644
--- a/.github/workflows/windows.yml
+++ b/.github/workflows/windows.yml
@@ -76,15 +76,19 @@ jobs:
# half only ever executes where PowerShell is native — so the one platform
# its PowerShell branch is written for was the one platform no job ran it on.
#
- # Its own job, and deliberately outside the `windows` label gate above: this
- # is a checkout and a few seconds of `sh`. No toolchain, no cache restore —
- # none of the economics the header's cost argument is about, which is the
- # ~1000s Rust job. Behind that gate, or sequenced after `cargo test` in the
- # same job, a pull request touching `hooks/` would still get no Windows hook
- # coverage unless someone remembered the label, and a Rust failure would stop
- # the shell suite from reporting at all.
+ # Its own job so a Rust failure cannot stop the shell suite from reporting,
+ # but gated behind the `windows` label like `test` above. The project keeps
+ # Windows off per-PR feedback by default (see the header's cost argument), so
+ # a pull request touching `hooks/` opts in with the `windows` label, the same
+ # as any other platform-sensitive change; it also runs nightly and on manual
+ # dispatch. (The job is cheap — a checkout and a few seconds of `sh` — but
+ # consistency with the fast-CI-per-merge rule wins over an every-PR carve-out.)
hooks:
name: hook bundle (windows-latest)
+ # On a pull request, only when explicitly opted in (same as `test`).
+ if: >-
+ github.event_name != 'pull_request' ||
+ contains(github.event.pull_request.labels.*.name, 'windows')
runs-on: windows-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1