Skip to content

Address review feedback from #1838 (Vag)#1840

Merged
pinin4fjords merged 2 commits into
devfrom
address-vag-1838-feedback
May 7, 2026
Merged

Address review feedback from #1838 (Vag)#1840
pinin4fjords merged 2 commits into
devfrom
address-vag-1838-feedback

Conversation

@pinin4fjords

Copy link
Copy Markdown
Member

Picks up the actionable points from @vagkaratzas's review on #1838.

Channel.xchannel.x in local code

Vag flagged a few Channel.of leftovers and asked whether nextflow lint would catch them (it does). Lowercased every uppercase Channel. reference in local test files (subworkflows/local/align_star/tests/*, subworkflows/local/utils_nfcore_rnaseq_pipeline/tests/main.pipeline_completion.workflow.nf.test, modules/local/star_genomeparams_upgrade/tests/main.nf.test) and the one in workflows/rnaseq/main.nf.

nf-core/ components are deliberately untouched - those would need upstream PRs and SHA bumps via nf-core modules update, which is out of scope here.

outputDir in the PIPELINE_COMPLETION test

Vag asked whether input[3] = "${outputDir}" in the pipeline_completion test was actually scoped to the nf-test sandbox or leaking to pipeline-level. Verified on the VM:

  • ${outputDir} is the per-test sandbox (.nf-test/tests/<id>/output), good.
  • The outdir workflow input is consumed by completionEmail() only when email || email_on_fail is set. Both are null in this test, so input[3] is unused on this code path.
  • However, nextflow.config wires report.file, timeline.file, trace.file, dag.file against params.outdir, which is null at the test level. That's why a literal null/pipeline_info/ directory was being created in the test sandbox.

Fix: add a params { outdir = "${outputDir}" } block to the test so the Nextflow execution reports land in output/pipeline_info/ instead. Verified the null/ directory no longer appears post-fix and the test still passes.

docs/CONTRIBUTING.md

Replaced the empty <!-- TODO nf-core: ... --> placeholder under "Pipeline specific contribution guidelines" with rnaseq-specific notes: test profile families, CI skip env vars (SKIP_GPU / SKIP_SENTIEON / SKIP_PARABRICKS), test data sources, the "edit nf-core modules upstream, not in-tree" rule, conf/modules/ config split, version-reporting topic (and the templated-module exception), --genome catalogues, snapshot conventions, and .nftignore. Kept it tight, no walls of prose.

CHANGELOG

Adds a #1840 entry under the 3.26.0 release section.

Test plan

  • pipeline_completion test passes on VM, no null/ dir
  • align_star tests (rg, extra_args) pass on VM after Channel.xchannel.x rewrite
  • star_genomeparams_upgrade module tests pass on VM
  • CI nf-test passes
  • Linting passes

🤖 Generated with Claude Code

pinin4fjords and others added 2 commits May 7, 2026 14:00
Three actionable points from Vag's #1838 review:

- Lowercase Channel.x -> channel.x in local test files and
  workflows/rnaseq/main.nf. nf-core component changes deferred
  (would need an upstream PR per file)
- pipeline_completion test: pin params.outdir = "${outputDir}" so
  Nextflow's report/timeline/trace/dag files (wired against
  params.outdir in nextflow.config) land in the nf-test sandbox
  instead of a literal null/pipeline_info/ directory. Verified
  on the VM
- Populate the previously empty "Pipeline specific contribution
  guidelines" section in docs/CONTRIBUTING.md with rnaseq-specific
  notes: test profiles, CI skip env vars, test data sources,
  module conventions, .nftignore, snapshots, version-reporting
  topic, --genome catalogues, CHANGELOG style

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented May 7, 2026

Copy link
Copy Markdown

nf-core pipelines lint overall result: Passed ✅ ⚠️

Posted for pipeline commit a1e4ca3

+| ✅ 201 tests passed       |+
#| ❔  21 tests were ignored |#
!| ❗   8 tests had warnings |!
Details

❗ Test warnings:

  • nextflow_config - Config manifest.version should end in dev: 3.26.0
  • pipeline_todos - TODO string in awsfulltest.yml: You can customise AWS full pipeline tests as required
  • pipeline_todos - TODO string in nextflow.config: Specify any additional parameters here
  • pipeline_todos - TODO string in main.nf: Optionally add in-text citation tools to this list.
  • pipeline_todos - TODO string in main.nf: Optionally add bibliographic entries to this list.
  • pipeline_todos - TODO string in main.nf: Only uncomment below if logic in toolCitationText/toolBibliographyText has been filled!
  • pipeline_todos - TODO string in base.config: Check the defaults for all processes
  • pipeline_todos - TODO string in methods_description_template.yml: #Update the HTML below to your preferred methods description, e.g. add publication citation for this pipeline

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 4.0.2
  • Run at 2026-05-07 13:07:15

@vagkaratzas vagkaratzas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@pinin4fjords pinin4fjords enabled auto-merge May 7, 2026 13:19
@pinin4fjords pinin4fjords merged commit b4605c4 into dev May 7, 2026
82 checks passed
@pinin4fjords pinin4fjords deleted the address-vag-1838-feedback branch May 7, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants