ci: thirteen WAI workflows run only when the pull request's own diff touches them #252

Merged

dcharlot merged 2 commits from ci/gate-on-pr-diff into main 2026-10-14 10:09:41 -04:00

Conversation 0 Commits 2 Files changed 15 +395 -4

dcharlot commented 2026-10-14 03:41:53 -04:00

Owner

Copy link

Thirteen WAI workflows now run only when the pull request's own diff touches their paths.

Why

This forge matches a workflow's paths: filter against the push, not the pull request (measured earlier: a jcp-only change ran 2 workflows on a fresh branch and 15 after a rebase). So every merge of main into a branch fired nearly every WAI workflow, whatever the pull request changed. That includes the three-platform conformance matrix, the Kani shards, the vector and operator legs, and the hour-long neural and JPEG AI end-to-end runs. Merges of main are routine here, and these runs filled the queue.

wai-pack and wai-web-reach already guarded against this with scripts/pr-touches-paths.py. This applies the same gate to the rest.

What changes

In each of the 13 workflows:

• a job relevant ("does this change touch it") runs on linux-arm64, a few seconds, and answers whether base...head touches any path in the workflow's own paths: lists;
• every other job gets needs: relevant and if: needs.relevant.outputs.run == 'true'. The one existing condition (conformance's spec-vector-coupling, pull requests only) is kept, joined with &&.

The gate fails open: a push to main, a scheduled run, or a diff it cannot compute answers true, so those run everything as before. Nothing else in the workflows changes.

The workflows: wai-conformance, wai-formal-verification, wai-vector, wai-ops, wai-quantum-webgpu, conformance, wai-energy-receipts, wai-byte-equality, wai-jpegai-e2e, wai-neural-e2e, wai-sota-vectors, wai-neural-gates and wai-web-wasm.

Evidence

• Every non-gate job in the 13 files depends on relevant and is conditioned on it; checked by parsing each file.
• The concurrency check passes.
• Each workflow lists its own file among its paths, so on this pull request every gate answers true and every workflow runs in full. That is the end-to-end test of the gate's true path. The false path is the one wai-pack and wai-web-reach have used for weeks.

🤖 Generated with Claude Code

Thirteen WAI workflows now run only when the pull request's own diff touches their paths. ## Why This forge matches a workflow's `paths:` filter against the push, not the pull request (measured earlier: a jcp-only change ran 2 workflows on a fresh branch and 15 after a rebase). So every merge of main into a branch fired nearly every WAI workflow, whatever the pull request changed. That includes the three-platform conformance matrix, the Kani shards, the vector and operator legs, and the hour-long neural and JPEG AI end-to-end runs. Merges of main are routine here, and these runs filled the queue. `wai-pack` and `wai-web-reach` already guarded against this with `scripts/pr-touches-paths.py`. This applies the same gate to the rest. ## What changes In each of the 13 workflows: - a job `relevant` ("does this change touch it") runs on `linux-arm64`, a few seconds, and answers whether `base...head` touches any path in the workflow's own `paths:` lists; - every other job gets `needs: relevant` and `if: needs.relevant.outputs.run == 'true'`. The one existing condition (`conformance`'s `spec-vector-coupling`, pull requests only) is kept, joined with `&&`. The gate fails open: a push to main, a scheduled run, or a diff it cannot compute answers `true`, so those run everything as before. Nothing else in the workflows changes. The workflows: `wai-conformance`, `wai-formal-verification`, `wai-vector`, `wai-ops`, `wai-quantum-webgpu`, `conformance`, `wai-energy-receipts`, `wai-byte-equality`, `wai-jpegai-e2e`, `wai-neural-e2e`, `wai-sota-vectors`, `wai-neural-gates` and `wai-web-wasm`. ## Evidence - Every non-gate job in the 13 files depends on `relevant` and is conditioned on it; checked by parsing each file. - The concurrency check passes. - Each workflow lists its own file among its paths, so on this pull request every gate answers `true` and every workflow runs in full. That is the end-to-end test of the gate's `true` path. The `false` path is the one `wai-pack` and `wai-web-reach` have used for weeks. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-10-14 03:41:53 -04:00

ci: thirteen WAI workflows run only when the pull request's own diff touches them ... c392092d84

The forge matches a workflow's paths: against the push, not the pull request,
so merging main into a branch fired every path-filtered workflow whatever the
pull request changed. wai-pack and wai-web-reach already guarded against this
with scripts/pr-touches-paths.py; wai-conformance, wai-formal-verification,
wai-vector, wai-ops, wai-quantum-webgpu, conformance, wai-energy-receipts,
wai-byte-equality, wai-jpegai-e2e, wai-neural-e2e, wai-sota-vectors,
wai-neural-gates and wai-web-wasm now do too: a light job on linux-arm64
answers whether the pull request's diff touches the workflow's paths, and every
other job waits on it. A push to main, a schedule, or anything the script
cannot determine answers true.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot added 1 commit 2026-10-14 04:21:46 -04:00

pr-touches-paths: a comment inside a path list no longer ends it ... 26a6c1454d

The parser stopped reading a paths: list at its first comment line, so every
glob after it was dropped and a pull request touching only those paths was
answered false: its workflow's tests skipped, silently. wai-http, which has
used this gate for weeks, was read as 10 of its 41 paths. The list now
continues past comments and blank lines, and a trailing comment is not part of
a glob; every workflow's list is read exactly as its YAML states it. The
self-test gains the case, and fails it with the old parser.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot merged commit 86785571a9 into main 2026-10-14 10:09:41 -04:00

dcharlot referenced this pull request from a commit 2026-10-14 10:09:41 -04:00

Merge pull request 'ci: thirteen WAI workflows run only when the pull request's own diff touches them' (#252) from ci/gate-on-pr-diff into main

dcharlot referenced this pull request from a commit 2026-10-14 11:03:58 -04:00

Merge origin/main (at 86785571, with #243-#246, #250, #252) into wai/d2c-m2-m3

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!252

No description provided.