Fastqc thread fix

[jfy133]

PR checklist

To close #879

• [x] This comment contains a description of changes (with reason).
• [ ] If you've fixed a bug or added code that should be tested, add tests!
  • [ ] If you've added a new tool - add to the software_versions process and a regex to scrape_software_versions.py
  • [ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • [ ] If necessary, also make a PR on the nf-core/eager branch on the nf-core/test-datasets repository.
• [x] Make sure your code lints (nf-core lint .).
• [x] Ensure the test suite passes (nextflow run . -profile test,docker).
• [x] Usage Documentation in docs/usage.md is updated.
• [x] Output Documentation in docs/output.md is updated.
• [x] CHANGELOG.md is updated.
• [x] 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 @jfy133,

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!

[github-actions[bot]]

YAML 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 yaml-lint
  • Install npm then install yaml-lint (npm install -g yaml-lint)
• Fix the markdown errors
  • Run the test locally: yamllint $(find . -type f -name "*.yml" -o -name "*.yaml")
  • Fix any reported errors in your YAML files

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

We highly recommend setting up yaml-lint 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!