`cli` Workflow failed when using `--only` or `--end` options
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Details
Whenever i am using the --only or --end CLI option the workflow execution always end with a failed status and no final output gets generated. A quick fix for this is to remove the "next":{}" option in the workflow.json execution plan for the step that you want the execution to end. See the attached video below
Additional Context 👇🏽
https://github.com/user-attachments/assets/41553754-75d4-473a-bd4b-80602b25aa00
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a workflow run with the --only and --end CLI options, then inspect the generated workflow.json execution plan, especially the next option on the terminating step. Done means these options produce a successful workflow status and final output without requiring the reported workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100