You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bc16625
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ci): derive a gate's population through composite actions, not just workflows
Six gates rooted their population at `.github/workflows` and none read
`.github/actions/**`, so a command executed through a composite action was
audited by nothing while every one of them printed a scope line that reads as
coverage. The positive control is not vacuous:
`.github/actions/setup-pnpm/action.yml` already carries six `run:` steps.
- `scripts/pm/dispatch-gates.mjs` now follows `uses: ./.github/actions/NAME`
out of a workflow and reads that action's `runs:` steps, recursively and
cycle-safe, attributing the invocation to the CALLING workflow (which is what
CI schedules) with the action file carried beside it as `viaAction`.
- The other five gates are judged from their own sources and extended where the
population genuinely belongs: the Node pin census, the step-name quoting
scan, the shared self-test population two gates consume, and the
`bash -e` masking scan all read both roots now.
- Four comments in `.github/**` that named the old blind spot as a constraint
are corrected, because this diff is what makes them false.
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments