Skip to content

Fix strict syntax errors#491

Merged
JoseEspinosa merged 1 commit intodevfrom
fix-strict-syntax
Mar 19, 2026
Merged

Fix strict syntax errors#491
JoseEspinosa merged 1 commit intodevfrom
fix-strict-syntax

Conversation

@bentsherman
Copy link
Copy Markdown

Hi, just testing the pipeline with strict syntax for Nextflow 26.04. Feel free to take these changes if they make sense

NOTE: nf-core modules and subworkflows can be fixed properly by just updating them from nf-core/modules

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 19, 2026

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

Posted for pipeline commit 0c65ff9

+| ✅ 266 tests passed       |+
#| ❔   2 tests were ignored |#
!| ❗   7 tests had warnings |!
Details

❗ Test warnings:

  • pipeline_todos - TODO string in nextflow.config: Optionally, you can add a pipeline-specific nf-core config at https://github.com/nf-core/configs
  • pipeline_todos - TODO string in nextflow.config: Update the field with the details of the contributors to your pipeline. New with Nextflow version 24.10.0
  • 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
  • pipeline_todos - TODO string in base.config: Check the defaults for all processes
  • 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!

❔ Tests ignored:

  • nextflow_config - Config default ignored: params.bamtools_filter_pe_config
  • nextflow_config - Config default ignored: params.bamtools_filter_se_config

✅ Tests passed:

Run details

  • nf-core/tools version 3.5.2
  • Run at 2026-03-19 15:02:08

@JoseEspinosa
Copy link
Copy Markdown
Member

Thanks @bentsherman! Actually, we are working with @Kevin-Brockers in updating modules, so I think it would make sense to wait until #487 is merged to update this PR

Copy link
Copy Markdown
Member

@JoseEspinosa JoseEspinosa left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks @bentsherman ❤️

@JoseEspinosa JoseEspinosa merged commit d8b98cd into dev Mar 19, 2026
20 checks passed
@ewels ewels deleted the fix-strict-syntax branch March 19, 2026 17:19
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