-
Notifications
You must be signed in to change notification settings - Fork 813
Important! Template update for nf-core/tools v3.4.1 #1614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
Merged dev branch into nf-core-template-merge-3.4.1, resolving conflicts by keeping pipeline-specific features while adopting template improvements. ## Conflict resolutions: ### Infrastructure improvements (adopted from template): - Update nf-test to v0.9.3 - Update minimum Nextflow version to 25.04.0 - Add new help system parameters (--help, --help_full, --show_hidden) - Update utility subworkflow git_sha values - Adopt `removeNextflowVersion` function for test snapshots - Use vars.AWS_S3_BUCKET instead of secrets for non-sensitive config ### Pipeline-specific features (retained): - Keep aligner matrix testing (star_salmon, star_rsem) in AWS full tests - Retain Sentieon authentication environment variables - Keep commit-pinned test data URL for reproducibility - Preserve pipeline metadata and real Zenodo DOI - Maintain existing CHANGELOG format ### Merged additions: - Combined test ignore patterns (both pipeline-specific and template) - Added both fastqc pattern variants for compatibility All changes follow the principle of preserving pipeline functionality while adopting template infrastructure improvements for better maintainability. Follows merge patterns from nf-core/sarek#2031 and guidance from https://nf-co.re/docs/tutorials/sync/merging_automated_prs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
|
jfy133
reviewed
Nov 13, 2025
Member
jfy133
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor fix for something that was borked in the template but otherwise LGTM
Co-authored-by: James A. Fellows Yates <[email protected]>
Member
|
Thanks @FriederikeHanssen @jfy133 ! |
mashehu
approved these changes
Nov 13, 2025
pinin4fjords
added a commit
to pontushojer/nfcore-rnaseq
that referenced
this pull request
Nov 13, 2025
- Add entry for PR nf-core#1613: Fix broken link and add latest kit version for Takara UMI prep - Add entry for PR nf-core#1614: Template update for nf-core/tools v3.4.1 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
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.
Version
3.4.1of nf-core/tools has just been released with updates to the nf-core template. This automated pull-request attempts to apply the relevant updates to this pipeline.Please make sure to merge this pull-request as soon as possible, resolving any merge conflicts in the
nf-core-template-merge-3.4.1branch (or your own fork, if you prefer). Once complete, make a new minor release of your pipeline.For instructions on how to merge this PR, please see https://nf-co.re/docs/contributing/sync/.
For more information about this release of nf-core/tools, please see the
v3.4.1release page.✅ Merge Conflicts Resolved
All merge conflicts have been resolved following nf-core best practices and the patterns from nf-core/sarek#2031.
Resolution Strategy
Conflicts were resolved by keeping pipeline-specific features while adopting template infrastructure improvements:
Template Infrastructure Improvements (Adopted)
--help,--help_full,--show_hiddenwith improved formattingvars.AWS_S3_BUCKETinstead of secrets for non-sensitive configTemplate Issues Fixed
aws.client.anonymoussetting as it breaks full size tests (see Slack discussion)get_topics→get_description) and missing closing parenthesis in jq commandPipeline-Specific Features (Retained)
removeFromYamlMap()to exclude entire Workflow section (both Nextflow and pipeline versions)## dev - xxxx-xx-xxconventionMerged Additions
Files with Conflicts Resolved
10 files resolved (click to expand)
.github/workflows/awsfulltest.yml- AWS testing configuration.github/workflows/nf-test.yml- nf-test workflow configurationCHANGELOG.md- Development version headermain.nf- Pipeline initialization parametersmodules.json- Module and subworkflow versionsnextflow.config- Pipeline configuration and manifestro-crate-metadata.json- Pipeline metadatasubworkflows/local/utils_nfcore_rnaseq_pipeline/main.nf- Utility subworkflowtests/.nftignore- Test snapshot ignore patternstests/default.nf.test- Test configurationAdditional Updates
rocrate_readme_syncfix to sync RO-Crate description with README.mdTesting Recommendations
nf-core lintto verify template complianceReferences
🤖 Conflict resolutions by Claude Code