Repository navigation
Conversation
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The change is a small, additive, backwards-compatible schema extension that matches the linked issue’s request.
Review effort: Lite
Findings: None
What changed in this PR
This PR updates the workflow JSON Schema to support specifying a working directory for RunShell, addressing issue #1191 so shell commands can execute with an explicit working directory rather than inheriting the workflow application’s startup directory.
Changes:
- Adds an optional
directorystring property to theRunShell.shellconfiguration object. - Documents the new property as the working directory used when running the shell command.
| File | Description |
|---|---|
| schema/workflow.yaml | Extends the RunShell schema to allow an optional working-directory (directory) for shell execution. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
@cvgaviao can you please also add a description of this new property to the |
|
@cvgaviao one more thing, you must commit with verified signatures. |
|
@ricardozanini , ok I will do it tonight. |
| | command | `string` | `yes` | The shell command to run | | ||
| | stdin | `string` | `no` | A runtime expression, if any, to the shell command as standard input (stdin).| | ||
| | arguments | `string[]` | `no` | A list of the arguments, if any, of the shell command to run | | ||
| | directory | `string` | `no` | The working directory, if any, in which to run the shell command. | |
| - Bar | ||
| - Foo | ||
| - Bar | ||
| directory: /tmp |
Signed-off-by: Cristiano Gavião <cvgaviao@gmail.com>
It seems to be ok now. I will need to sign the other commits too. |
|
@cvgaviao can you have a look at the CI? |

Please specify parts of this PR update:
#1191
What this PR does:
Added property directory to RunShell
Additional information: