Is your feature request related to a problem? Please describe.
In a step, when I write code for a run: key, that code is completely unlinted by an appropriate linter, such as ShellCheck for shell scripts.
Describe the solution you'd like
Given that the shell used by run: has a known default, or can be specified with a defaults.run.shell in the workflow, it would be nice if the content of run: keys were run through the appropriate linter.
Additional context
The work-around here is to put all content one would otherwise write into a run: key into a separate file (per step.run -- so lots of files) and then just reference the file in the run:. This leads to a lot of tab and context switching on the part of the user as one ends up with a tab open for each step one has a run: in.
Is your feature request related to a problem? Please describe.
In a step, when I write code for a
run:key, that code is completely unlinted by an appropriate linter, such as ShellCheck for shell scripts.Describe the solution you'd like
Given that the shell used by
run:has a known default, or can be specified with adefaults.run.shellin the workflow, it would be nice if the content ofrun:keys were run through the appropriate linter.Additional context
The work-around here is to put all content one would otherwise write into a
run:key into a separate file (perstep.run-- so lots of files) and then just reference the file in therun:. This leads to a lot of tab and context switching on the part of the user as one ends up with a tab open for each step one has arun:in.