Skip to content

Conversation

@nf-core-bot
Copy link
Member

Version 3.2.1 of 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.2.1 branch (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.2.1 release page.

Copy link

@jonasscheid jonasscheid left a comment

Choose a reason for hiding this comment

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

LGTM 👍🏼
For next template merge, I would advise you to: create feature branch -> merge new template into feature branch -> resolve conflicts -> open PR feature branch to dev. That way you cannot mess up the PR from the nf-core bot

and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## v1.3.0dev - [2025-01-31]
## v1.3.0dev - [date]

Choose a reason for hiding this comment

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

Update changelog

Copy link
Collaborator

Choose a reason for hiding this comment

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

Uhm, do I need to change something here?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I guess the date here will be updated when release 1.3.0 is out. Merging like this for now ;)

Choose a reason for hiding this comment

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

I meant that you could add this PR in the #Changed section of CHANGELOG. By this everyone knows which template version your pipeline supports

@vagkaratzas
Copy link
Collaborator

LGTM 👍🏼 For next template merge, I would advise you to: create feature branch -> merge new template into feature branch -> resolve conflicts -> open PR feature branch to dev. That way you cannot mess up the PR from the nf-core bot

Thanks! Oh, yeah, that makes sense, I will!

@vagkaratzas vagkaratzas merged commit b8742b4 into dev May 12, 2025
9 checks passed
@vagkaratzas vagkaratzas deleted the nf-core-template-merge-3.2.1 branch May 22, 2025 11:09
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.

3 participants