Patch 2.5.1

[TCLamnidis]

Patch release 2.5.1 - Bopfingen

Closes #1036 Closes #1037 Closes #1047 Closes #1048 Closes #1049 Closes #1051

PR checklist

• [x] This comment contains a description of changes (with reason).
• [x] Make sure your code lints (nf-core lint .).
• [ ] Ensure the test suite passes (nextflow run . -profile test,docker).
• [ ] Usage Documentation in docs/usage.md is updated.
• [ ] Output Documentation in docs/output.md is updated.
• [x] CHANGELOG.md is updated.
• [ ] README.md is updated (including new tool citations and authors/contributors).

[github-actions[bot]]

This PR is against the master branch :x:

• Do not close this PR
• Click Edit and change the base to dev
• This CI test will remain failed until you push a new commit

---

Hi @TCLamnidis,

It looks like this pull-request is has been made against the nf-core/eager master branch. The master branch on nf-core repositories should always contain code from the latest release. Because of this, PRs to master are only allowed if they come from the nf-core/eager dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page. Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

[github-actions[bot]]

Markdown linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks. To fix this CI test, please run:

• Install markdownlint-cli
  • On Mac: brew install markdownlint-cli
  • Everything else: Install npm then install markdownlint-cli (npm install -g markdownlint-cli)
• Fix the markdown errors
  • Automatically: markdownlint . --config .github/markdownlint.yml --fix
  • Manually resolve anything left from markdownlint . --config .github/markdownlint.yml

Once you push these changes the test should pass, and you can hide this comment :+1:

We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!

[TCLamnidis]

All markdown linting fails for various reasons, but linting is fine locally (except for logos being outdated).

[TCLamnidis]

I will update the date in the changelog and make the release tomorrow