Skip to content

Pseudo-review: first release - #88

Open
ewels wants to merge 368 commits into
pesudo-review-template-4.3.0from
dev
Open

Pseudo-review: first release#88
ewels wants to merge 368 commits into
pesudo-review-template-4.3.0from
dev

Conversation

@ewels

@ewels ewels commented Sep 7, 2026

Copy link
Copy Markdown
Member

Warning

Not intended to be merged.
This PR is just to give a meaningful whole-pipeline diff for a first-release code view.

Because master is on a very old version of the template, much of the diff in #82 is from template updates.

This PR is to a branch that comes from template v4.0.3, which I believe is the latest version of the template that has been merged into dev. As a result, the diff should be a minimal version of "what's new in the pipeline versus the boilerplate template".

It's not intended for this PR to be merged. Once used for review, it can be closed and the branch discarded, then #8 merged and first release.

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

nf-core pipelines lint overall result: Passed ✅ ⚠️

Posted for pipeline commit d25e58a

+| ✅ 205 tests passed       |+
#| ❔   5 tests were ignored |#
#| ❔   1 tests had warnings |#
!| ❗   5 tests had warnings |!
Details

❗ Test warnings:

  • files_exist - File not found: conf/igenomes.config
  • files_exist - File not found: conf/igenomes_ignored.config
  • nextflow_config - Config manifest.version should end in dev: 1.0.0
  • readme - README contains the placeholder zenodo.XXXXXXX. This should be replaced with the zenodo doi (after the first release).
  • pipeline_todos - TODO string in README.md: Add citation for pipeline after first release. Uncomment lines below and update Zenodo doi and badge at the top of this file.

❔ Tests ignored:

❔ Tests fixed:

✅ Tests passed:

Run details

  • nf-core/tools version 4.1.0
  • Run at 2026-09-09 15:44:17

@ewels ewels left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Great stuff! Quick pass on the pipeline as an overview (not too much on the actual dataflow code and modules, on the assumption that it's already well tested there).

Looks great: some minor comments, but hopefully all quite quick to resolve.

Comment thread .github/workflows/awsfulltest.yml Outdated
Comment thread .github/PULL_REQUEST_TEMPLATE.md Outdated
Comment thread assets/methods_description_template.yml
Comment thread assets/multiqc_config.yml
Comment thread assets/multiqc_custom.css
@@ -0,0 +1,52 @@
/* Keep the internal row identifier available to MultiQC without displaying it. */

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This, in contrast, makes me nervous 😆

I think I get at what you're doing with most of this, though some of the CSS makes me wonder if you're papering over rendering issues that should be solved at MultiQC level. Please make issues if that's the case (can always cut this out of the pipeline in the future, doesn't need to be a blocker).

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

If it's okay, we will leave this as-is now and create a new issue to tackle this once the release is done

Comment thread subworkflows/local/utils_nfcore_datasync_pipeline/main.nf
Comment thread CHANGELOG.md Outdated
Comment thread nextflow.config
Comment thread nextflow_schema.json Outdated
Comment thread README.md Outdated
@delfiterradas

Copy link
Copy Markdown

Hi @ewels,
Thank you for taking the time to review the code, we really appreciate your suggestions!
I am currently working on implementing the changes in #89. The suggestions marked as resolved have already been addressed and I will continue implementing the rest
I can let you know when it is done. Thanks again!

@delfiterradas delfiterradas mentioned this pull request Sep 9, 2026
11 tasks
@delfiterradas

Copy link
Copy Markdown

Hi @ewels, I have merged the branch with the changes you suggested :)

When you have the time, would you mind taking a look at it again?

I think the only suggestion I didn't include for the time being is the MultiQC one (I have opened an issue to address that after the release), but please let me know if there is anything I have missed.

Thank you!

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.

7 participants