`Context access might be invalid` warning shows for `push`, not for `pull_request` event

[garysassano]

Describe the bug
See screenshots below.

To Reproduce
Steps to reproduce the behavior:

1. With this workflow '...'
2. Do this '...'
3. See error

Expected behavior
Context access might be invalid shows up for all kind of events where the context might be missing.

Screenshots

Package/Area

• Expressions
• Workflow Parser
• Language Service
• Language Server

Package Version
v1.x.y

Additional context
Add any other context about the problem here.

[garysassano]

Apparently, you access the head_commit property without specifying an event type (github.event.head_commit.messag), even though the structure of the payload should be correct according to the docs.

Also, technically the Context access might be invalid warning should always be displayed when accessing any event-specific context, since you have no guarantee of which event type triggered the workflow UNLESS the workflow specifies a single trigger, in which case that event type context would be guaranteed to be valid.

[johnseth97]

Also, technically the Context access might be invalid warning should always be displayed when accessing any event-specific context, since you have no guarantee of which event type triggered the workflow UNLESS the workflow specifies a single trigger, in which case that event type context would be guaranteed to be valid.

If that's the case, it would be nice to be able to suppress the warning. Maybe something similar to flake8, i.e. #github-actions-context-manually-verified posted at the end of the offending line.

[johnseth97]

You could try putting in a default value with the or operator

${{ <output> || <default_value> }}

[eric-nclusion]

I am using this hacky workaround, which works, but is not ideal:

${{ fromJson(toJson(github.event)).push.head.sha }}

This will suppress the warning.