Define the correct schema when creating a cross-org sub-workflow
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Description of feature
Cross-organisation sub-workflows need a different JSON Schema file to valid their meta.yml (because there are extra keys to define 3rd-party components).
The nf-core subworkflows create command could know that and modify the line accordingly, making it link to the current repository.
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
Start with the nf-core subworkflows create command and the template at nf_core/subworkflow-template/meta.yml, especially line 1. Determine how cross-organisation sub-workflows are identified and how the schema reference is currently selected. Done means cross-organisation metadata links to the current repository's schema while existing creation behavior remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100