You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
When executing a workflow through a project, output to worklflow/tmp #1455
This will load the current project and work out where my-workflow is from there.
When we do this, by default the output path will be my-workflow/output.json . Which is odd because the workflow lives in workflows/my-workflow. It means a messy new diff has been created and its not a nice experience.
It would be nicer to default the output to tmp/output.json, relative to the workflow.yaml file.
What about input paths? If I do -s input.hson should that be relattve to workflow/tmp? cwd? Perhaps if you do ./state.json we'll do it relative to the workspace root, but if you just do state.json we load it from /tmp. Then again its not hard to do -s tmp/input/json.
So what if we say that all input and output paths for a workflow are relative to the workflow yaml? If no path is included we do tmp/state.
Yes!! Mtuchi reported this a long time ago. I'm just doing some testing locally and it's super annoying. The CLI is getting quite opinionated and optimised about how it understands your local project and interacts with github... and then it goes and dumps your output files in a stupid place
Activity
josephjclark commentedon Oct 12, 2026
Yes!! Mtuchi reported this a long time ago. I'm just doing some testing locally and it's super annoying. The CLI is getting quite opinionated and optimised about how it understands your local project and interacts with github... and then it goes and dumps your output files in a stupid place