-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feat: Allow the shell to be configured for workflow command steps #5024
Conversation
Hi @anryko, thanks for this. Any chance you can follow the same pattern as the pre/post workflow hooks to have the ability to specify the I also see no reason to limit the shell to |
@X-Guardian sure, I'll do that. I would suggest to make |
e365fca
to
c7cbbe1
Compare
@X-Guardian I added support for |
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.
Nearly there @anryko. Once you have added the debug log lines, can you add some log snippets to the PR description as evidence that this functionality is working.
Signed-off-by: anryko <[email protected]>
Signed-off-by: anryko <[email protected]>
Signed-off-by: anryko <[email protected]>
Thanks for your work on this @anryko. You can test it by using one of the following container images: dev-debian-8285a0f or dev-alpine-8285a0f |
what
Added an option to define the shell for the custom workflow steps with the
command
filed, likerun
,env
, andmultienv
.why
command: bash -c "my inline shell script"
, but dealing with double quote escaping within the shell script is quite cumbersome.tests
references