-
Notifications
You must be signed in to change notification settings - Fork 14
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
Template update for nf-core/tools version 2.14.0 #90
Conversation
|
Version Please use #91 to merge in the new changes from the nf-core template as soon as possible. |
@maxulysse : Anything else I should do as part of "back to dev"? |
so this one replaces #89? |
I am unsure what is causing this, it could be a bug on nf-schema, we see the same behaviour with |
lint: | ||
files_unchanged: | ||
- .github/CONTRIBUTING.md | ||
- .github/CONTRIBUTING.md |
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.
why this file?
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.
You mean .github/CONTRIBUTING.md
? It is like that on the dev
-branch. I think this PR just adds a newline or something like that at the end of .nf-core.yml
.
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.
The template update modified only the new line. Adding this file will skip the linting test. You should do this only if you edited CONTRIBUTING.md
and don't want to lint it.
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.
I guess somebody put .github/CONTRIBUTING.md
in .nf-core.yml
because it was failing the linting test.
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.
ok let's deal with that in the other PR then
Currently, getting
"
WARN: Access to undefined parameter
fasta
-- Initialise it to a default value eg.params.fasta = some_value
WARN: Access to undefined parameter
monochromeLogs
-- Initialise it to a default value eg.params.monochromeLogs = some_value
"
@mirpedrol : As you can see, I did add both
fasta
andfasta_fai
tovalidationSchemaIgnoreParams
so why do I get that warning aboutfasta
being uninitialised?PR checklist
nf-core lint
).nf-test test main.nf.test -profile test,docker
).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).