Repository navigation
Document asset input in usage docs - #165
Merged
Merged
Conversation
Fill the Multiple genomes and Full asset file placeholders, and move the example assets link under the heading it belongs to. Also replace an em dash and an en dash, both non-ASCII and banned by the repository prose rules. Generated by OpenCode
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 4.1.0. For more documentation on how to update your pipeline, please see the Synchronisation documentation. |
|
This file contains hidden or 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
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
CHANGELOG.mdis updatednextflow_schema.jsonis updated (if needed)docs/usage.mdis updated (if needed)docs/output.mdis updated (if needed)assets/is updated (if needed)TODOcommentsDescription
Fills the two placeholder sections under Asset input in
docs/usage.md, both of which rendered a bareTODOon the website.Multiple genomesstates that a datasheet is a YAML list with one entry per genome and thatgenomeis the only required field. It explains whyspeciesandsourcemust be set, since the pipeline builds the published path fromspecies/source/genome, and shows a two-entry example with the output tree it produces. It also records that run flags are computed per entry, so genomes with different capabilities build independently in one run.Full asset filegives a worked example over realGRCh37decoypaths covering genome and annotation fields, a prebuilt index, and a GATK resource VCF with its tabix index and provenance, then lists the format rules. Supplying an artefact stops the pipeline building it, which I verified against therun_X: meta.X ? false : trueflags indatasheet_to_channel. Thevcf_*_vcffields take a path or a list, the TBI list pairs by position, and anullentry means the pipeline builds that index. The*_sourcefields become theAnnotation/<source>segment of the published path.The example assets link moves under
Full asset file. It previously sat after two empty headings, so it read as the conclusion of a section that still said TODO.This PR also replaces an em dash and an en dash. Both are non-ASCII and banned by the repository prose rules. The earlier deslop pass covered the roadmap and the PR bodies but not
docs/.Not changed
Line 9 keeps the template's
<!-- TODO nf-core: ... -->comment. It is tracked upstream, so removing it locally would be reverted by the next template sync.pipeline_todosstill reports it, which is whynf-core pipelines lintstays at 21 warnings: that check matchesTODO nf-core:markers, so the two bare TODOs removed here were never counted.Testing
prekpasses, including prettier.nf-core pipelines lint: 366 passed, 0 failed, 21 pre-existing warnings.Generated by OpenCode