I noticed that
INPUT_<UPPERCASEDINPUTNAME> environmental variables are not set for inputs defined in a
The blog post says you define them the same way as action inputs, but it doesn’t explicitly say that the environmental variables will be set. Since it uses the action inputs documentation as a reference though, I almost expected them to work the same way.
The documentation describes the format of the env variables for actions:
Here is a run showing it is not set
Either way it can be set manually through the
echo"::set-env .... " syntax so it’s not a huge deal. I just wondered if this was something that was considered.