Template updated 2.3.1 #139
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…core/quantms into dev � Conflicts: � .github/workflows/awsfulltest.yml � .github/workflows/awstest.yml � .github/workflows/ci.yml � .yamllint.yml � CHANGELOG.md � CITATIONS.md � README.md � assets/multiqc_config.yaml � docs/output.md � docs/usage.md � modules.json � modules/nf-core/modules/fastqc/main.nf � modules/nf-core/modules/fastqc/meta.yml � nextflow.config � nextflow_schema.json
|
Co-authored-by: Julianus Pfeuffer <pfeuffer@informatik.uni-tuebingen.de>
jpfeuffer
reviewed
Mar 24, 2022
jpfeuffer
reviewed
Mar 24, 2022
jpfeuffer
reviewed
Mar 24, 2022
.nf-core.yml
Outdated
| @@ -1,7 +1,7 @@ | |||
| repository_type: pipeline | |||
| lint: | |||
| files_unchanged: | |||
| - assets/multiqc_config.yaml | |||
| - assets/multiqc_config.yml | |||
There was a problem hiding this comment.
I fixed the linting on nf-core
There was a problem hiding this comment.
I removed it but now CI is failing
There was a problem hiding this comment.
The MultiQC linting was rewritten in this release, in the hope that it should not be necessary to ignore for most of the time. I'd be curious as to why you need it here..
There was a problem hiding this comment.
We were just confused with the meaning of order in MultiQC. I actually thought -123 would mean at the beginning of the report. Should be no linting errors anymore
There was a problem hiding this comment.
ok great 👍🏻
I have to check the docs every time for this kind of thing.. https://multiqc.info/docs/#order-of-module-and-module-subsection-output
Next, specify the
report_section_orderoption in your MultiQC config file. Modules and sections in the report are given a number ranging from 10 (section at bottom of report), incrementing by +10 for each section. You can change this number (eg. a very low number to always get at the bottom of the report or very high to always be at the top), or you can move a section to before or after another existing section (has no effect if the other named ID is not in the report).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR checklist
nf-core lint).nextflow run . -profile test,docker--outdir `).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).