[x] Feature branch is named feature/<module_name> for modules, or feature/<subworkflow_name> for subworkflows. For modules, if there is a subcommand use: feature/<module_name>/<module_subcommand>.
[x] If you've fixed a bug or added code that should be tested, add tests!
[x] If you've added a new tool - have you followed the module conventions in the contribution docs.
[x] Use nf-core data if possible for nf-tests. If not, use or add test data to mskcc-omics-workflows/test-datasets, following the repository guidelines, for nf-tests. Finally, if neither option is feasible, only add a stub nf-test.
[x] Remove all TODO statements.
[x] Emit the versions.yml file.
[x] Follow the naming conventions.
[x] Follow the parameters requirements.
[x] Follow the input/output options guidelines.
[x] Add a resource label.
[ ] Use Jfrog if possible to fulfil software requirements.
Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
PR checklist
Closes #126
feature/<module_name>for modules, orfeature/<subworkflow_name>for subworkflows. For modules, if there is a subcommand use:feature/<module_name>/<module_subcommand>.versions.ymlfile.label.nf-core modules --git-remote https://github.com/mskcc-omics-workflows/modules.git -b <module_branch> test <MODULE> --profile dockernf-core modules --git-remote https://github.com/mskcc-omics-workflows/modules.git -b <module_branch> test <MODULE> --profile singularitynf-core modules --git-remote https://github.com/mskcc-omics-workflows/modules.git -b <module_branch> test <MODULE> --profile conda