Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Small nits in pipeline template 4.2.1

Open Beginner friendly
#4,569 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@znorgaard is already working on this.

Since Oct 28, 2026.

  • #4570 by @znorgaard — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, python

Research direction

Start by locating the pipeline template files awsfulltest.yml, nextflow.config, .github/workflows/nf-test.yml, and the block-pipeline-outdir pre-commit hook script. Compare the nf-schema versions and upload-artifact comments, then check how the hook handles filenames. Done when the three listed inconsistencies are resolved in the template.

Written by the indexing model from the issue text.

Description

template
Description of the bug

Found a handful of small nits when migrating over.

  • awsfulltest.yml and nextflow.config declare different nf-schema versions
  • block-pipeline-outdir pre-commit hook ignores the files it is given. Suggested fix: set pass_filenames: false on the hook, or have the script iterate over "$@".
  • Inconsistent version comment on upload-artifact. .github/workflows/nf-test.yml pins actions/upload-artifact with the comment # v7, while every other template workflow labels the same SHA # v7.0.2.
Command used and terminal output
`nf-core pipelines sync  # nf-core/tools 4.2.1`
System information
  • nf-core/tools 4.2.1
  • Nextflow 25.10.4 and 26.10.4
  • Pipeline: nf-core/fastquorum (TEMPLATE branch at the 4.2.1 sync commit)
Dominant language
Python
Stars
327
Forks
266
Avg merge
1d 23h
Merged PRs (30d)
33

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nf-core/tools

All issues in nf-core/tools

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.