-
Notifications
You must be signed in to change notification settings - Fork 967
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify details for defaults, shell, and working-dir #607
Conversation
In this commit, I clarify some details for our implementation of shell and working-dir (cc: @ericsciple )
|
||
The composite action author will be required to set the `shell` and `workingDir` of the composite action. Moreover, the composite action author will be able to explicitly set the shell for each composite run step. The workflow author will not have the ability to change these attributes. | ||
### Shell and Working-directory | ||
For each run step in a composite action, the action author can set the `shell` and `working-directory` attributes for that step. These attributes are optional for each run step - by default, the `shell` is set to whatever default value is associated with the runner os (ex: bash =\> Mac). Moreover, the composite action author can map in values from the `inputs` for it's `shell` and `working-directory` attributes at the step level for an action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These attributes are optional for each run step - by default, the
shell
is set to whatever default value is associated with the runner os
This doesn't appear to be true. Removing the shell
attribute from any run
step of a composite action results in:
The template is not valid ... Required property is missing: shell
In this commit, I clarify some details for our implementation of shell and working-dir (cc: @ericsciple )