Skip to content

Context access might be invalid: is too aggressive #239

@jsoref

Description

@jsoref

message: `Context access might be invalid: ${e.keyName}`,

If I write some yaml like this:

       with:
          ssh_key:   '${{ '' || secrets.CHECK_SPELLING || '' }}'

(The leading '' || has no value, but the point is regardless of how cautious one tries to be, this warning complains unequivocally.)

I get:
Context access might be invalid: CHECK_SPELLING

It might be true that the access might be invalid, but the expression as written accepts that fact, and GitHub's design doesn't offer an alternative, so, given that something like this is more or less exactly what GitHub wants people to do.

Doing what a designer wants you to do should not generate an error nor a warning.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions