-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix igenomes_base in nextflow_schema #479
Conversation
|
Removed the igenomes_base from the nextflow schema, not sure why the CI test checking if the PR is pointing towards dev is failing, should be ok |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you not using igenomes?
Yes we are, igenomes_base was added into the nextflow_schema as a quickfix, I'm reverting this fix which is no longer needed. With the recent update in the nf-core template, the parameters from schema ignore were not being properly parsed, making the linting fail due to not seeing an entry for the igenomes_base parameter in the nextflow_schema. This was already patched, so we no longer need to have the igenomes_base entry in the nextflow_schema |
but if you use igenomes, why don't you want to use |
We want to use igenomes_base and we are using igenomes_base. We just don't need to have it the schema, but we still have it as a parameter. https://nfcore.slack.com/archives/CL66GAJBF/p1729006915504669 |
the schema should cover every parameter |
@mashehu Should be good to go now, let me know if you have any comments |
PR checklist
nf-core pipelines 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).