Skip to content
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

Release 2.3 - This time for real #244

Merged
merged 6 commits into from
Jun 17, 2024
Merged

Release 2.3 - This time for real #244

merged 6 commits into from
Jun 17, 2024

Conversation

WackerO
Copy link
Collaborator

@WackerO WackerO commented Jun 17, 2024

Second release PR after I found a bug in the previous one

PR checklist

  • 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 - have you followed the pipeline conventions in the contribution docs
  • Make sure your code lints (nf-core lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

Copy link

This PR is against the master branch ❌

  • 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 @WackerO,

It looks like this pull-request is has been made against the qbic-pipelines/rnadeseq 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 qbic-pipelines/rnadeseq 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!

Copy link

github-actions bot commented Jun 17, 2024

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit 169e70e

+| ✅ 171 tests passed       |+
#| ❔  17 tests were ignored |#
!| ❗   3 tests had warnings |!

❗ Test warnings:

  • nextflow_config - Config manifest.version should end in dev: 2.3
  • readme - README did not have a Nextflow minimum version badge.
  • schema_lint - Parameter input is not defined in the correct subschema (input_output_options)

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 2.14.1
  • Run at 2024-06-17 12:27:46

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Sabrina Krakau <[email protected]>
@skrakau
Copy link
Collaborator

skrakau commented Jun 17, 2024

Even if the PR does not contain a lot of changes, it would be helpful (and best-practice) to briefly describe what this PR is about, and what the previous bug was about.

@@ -193,6 +193,16 @@
"type": "string",
"default": "${projectDir}/assets/references.bibtex",
"description": "Reference bibtex file for the report, should not be changed."
},
Copy link
Contributor

Choose a reason for hiding this comment

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

why is it a variable if it shouldn't be changed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

There was apparently some nextflow change; now it seems the files in assets/ cannot be accessed by processes unless they are provided to the respective module as channels.

Copy link
Collaborator

@skrakau skrakau left a comment

Choose a reason for hiding this comment

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

Apart from the typo it looks good to me!

@WackerO WackerO merged commit 163c7ee into master Jun 17, 2024
35 of 36 checks passed
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