This is a bug fix:
nextflow run nf-core/ampliseq -r 2.5.0 -profile test_reftaxcustom,singularity --outdir results --dada_ref_tax_custom_sp false --skip_dada_addspecies
was fine but
nextflow run nf-core/ampliseq -r 2.6.1 -profile test_reftaxcustom,singularity --outdir results --dada_ref_tax_custom_sp false --skip_dada_addspecies
failed with
ERROR ~ No such variable: ch_addspecies
Obviously that function was broken after introduction, so I added a test in the new test_failed.conf that should prevent that in future.
PR checklist
[x] This comment contains a description of changes (with reason).
[x] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/ampliseq branch on the nf-core/test-datasets repository.
[x] Make sure your code lints (nf-core lint).
[x] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[x] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).
This is a bug fix:
nextflow run nf-core/ampliseq -r 2.5.0 -profile test_reftaxcustom,singularity --outdir results --dada_ref_tax_custom_sp false --skip_dada_addspecies
was fine butnextflow run nf-core/ampliseq -r 2.6.1 -profile test_reftaxcustom,singularity --outdir results --dada_ref_tax_custom_sp false --skip_dada_addspecies
failed withERROR ~ No such variable: ch_addspecies
Obviously that function was broken after introduction, so I added a test in the new
test_failed.conf
that should prevent that in future.PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).