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
Actions: AssociationIfCheck should not protect events that do not populate the checked field
Same problem as EventActorIfCheck had. A condition like
'github.event.pull_request.author_association != NONE' on a workflow
triggered by issues events is always true since
github.event.pull_request is not populated there, but it still counted
as a protective check for those events.
Bind the matched context prefix in the characteristic predicate and
require contextTriggerDataModel to populate it for the event, following
the pattern from #22368. Existing TOCTOU alerts on vacuous gates
migrate to the untrusted-checkout critical query, since a vacuous gate
is no protection rather than raceable protection.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4084febb-f9c7-44df-baf3-c8be8e9932a7
* Checks on author association fields read from the event payload (e.g. `github.event.pull_request.author_association`) now only count as protection for events whose payload actually populates that field. Previously, a condition such as `github.event.pull_request.author_association != 'NONE'` on a workflow triggered by `issues` events was treated as a protective check even though `github.event.pull_request` is not populated for `issues` events, which makes the condition vacuous. This change may result in more alerts for queries using the `ControlCheck` class.
0 commit comments