Create a workflow to test module multiqc compatibility
Open
Nobody has claimed this yet.
wishlist
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
Since MultiQC supports a ton of software, we should confirm that the modules are passing/naming the files correctly. Not sure if this should live in the modules repo or in it's own repo. Probably here to make sure it stays in sync.
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 by reviewing the existing module files and how their output files are named, then check how MultiQC compatibility would be exercised. The work is done when a workflow reliably tests the modules against MultiQC and confirms that the expected files are passed and named correctly; the issue leaves the repository location undecided.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100