Skip to content

Decouple SCM classes in Nextflow independent module#6740

Draft
jorgee wants to merge 1 commit intomasterfrom
nf-298-platform-modules-v2
Draft

Decouple SCM classes in Nextflow independent module#6740
jorgee wants to merge 1 commit intomasterfrom
nf-298-platform-modules-v2

Conversation

@jorgee
Copy link
Contributor

@jorgee jorgee commented Jan 20, 2026

This pull request refactors the Nextflow asset management to decouple the SCM functionality form the rest of the Nextflow code.

Two new packages are created

  • nf-scm: Contains the SCM classes decouple from the rest of nextflow classes

  • nf-utils: Contains util clases required by SCM and the rest of nextflow

alternative for #6719

Signed-off-by: jorgee <jorge.ejarque@seqera.io>
@netlify
Copy link

netlify bot commented Jan 20, 2026

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit 3b30754
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/696fd8ea9ca7d2000879d95a

@pditommaso
Copy link
Member

I have the feeling that #6719 is a better approach. What's the advantage of this PR ?

@jorgee
Copy link
Contributor Author

jorgee commented Jan 21, 2026

In this PR, classes are not depending on nf-commons. only nf-utils and nf-scm are required to move to libseqera. In the other, you require to get nf-commons, nf-secrets, nf-config and nf-scm.

@pditommaso
Copy link
Member

I understand but in my view this refactor is going too far. I think should stay in nextflow repository, other apps still benefits avoiding to import all nextflow runtime full deps tree.

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.

2 participants