For a new software (Sidle) I produced a container and deposited it at dockerhub. The processes that use that software did so with container 'docker.io/d4straub/pipesidle:0.1.0-beta'. My proposal to put the tool (pypi packaged) to conda was rejected by the developer of said tool. I generated the container with Dockerfile & environment.yml. This container was now pushed to quay.io/nf-core, therefore now retrieved by container 'nf-core/pipesidle:0.1.0-beta'.
PR checklist
[x] This comment contains a description of changes (with reason).
[ ] 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.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,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).
For a new software (Sidle) I produced a container and deposited it at dockerhub. The processes that use that software did so with
container 'docker.io/d4straub/pipesidle:0.1.0-beta'
. My proposal to put the tool (pypi packaged) to conda was rejected by the developer of said tool. I generated the container with Dockerfile & environment.yml. This container was now pushed toquay.io/nf-core
, therefore now retrieved bycontainer 'nf-core/pipesidle:0.1.0-beta'
.PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,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).