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
I'm trying to leverage this action with a self-hosted runner using a container (not the runner agent). I'm not really doing anything too fancy, but when the step runs, it fails with the error Error: Input does not meet YAML 1.2 "Core Schema" specification: log-public-key.
When reviewing the action.yml file is vscode, I did notice that the Github Actions vscode extension was flagging the default value for the input in question. Stating Incorrect type. Expected "string".yaml-schema: GitHub Action.
The text was updated successfully, but these errors were encountered:
Testing update - The issue seems to be specific to using the action within a container. While using the Linux self-hosted runner directly and no a container hosted on the Linux self-hosted runner, the action works as expected.
Hello,
I'm trying to leverage this action with a self-hosted runner using a container (not the runner agent). I'm not really doing anything too fancy, but when the step runs, it fails with the error Error: Input does not meet YAML 1.2 "Core Schema" specification: log-public-key.
When reviewing the action.yml file is vscode, I did notice that the Github Actions vscode extension was flagging the default value for the input in question. Stating Incorrect type. Expected "string".yaml-schema: GitHub Action.
The text was updated successfully, but these errors were encountered: