Support sub-pipeline execution
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 124
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Discuss the designs here.
Contributor guide
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
The issue only asks contributors to discuss designs for supporting sub-pipeline execution and names no files, tests, or entry points. Start by reviewing the repository's pipeline implementation and existing discussions, then establish the design and acceptance criteria before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100