Migration to topic channels
Open
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
Starting an issue to track. Probably gonna need a hackathon for this 🙃
docs
### Tasks
- [ ] Update tools linting
- [ ] PoC PR
- [ ] Bump Nextflow version in pipelines, template, and modules CI
- [ ] Update pipeline code to use topics
- [ ] Create a "validate versions.yml" helper function
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 linked Nextflow channel documentation and inspect the repository's pipeline, template, modules CI, linting tools, and versions.yml references. The task list identifies the intended migration areas, but no files or tests are named; done means completing the listed topic-channel migration and its version-validation and CI updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100