Hello friends, We are currently testing workflow modules for Nextflow, including the auto-import of nf-core subworkflows into the Nextflow registry One design decision we made is that process modules and workflow modules exist in the same namespace, so there cannot be a process and a workflow with the same name The nf-core/modules repo has one such conflict: • github.com/nf-core/modules/…/deepvariant • github.com/nf-core/modules/…/deepvariant In order for the registry to be able to import both modules, one of them will need to be renamed

We can figure something out

We should remove the module

Let's go then

just over two years. So let's remove that

@Ben Sherman: is the problem with the module named

deepvariant

? Or with the module*s* that live in sub-directories of

deepvariant

?

The subworkflow deepvariant should be called

bam_deepvariant

if we want to be fussy 😉

dwight true

@Simon Pearce I finally understand what you were asking. The nested

nf-core/deepvariant/*

processes are fine, they will not conflict with the

nf-core/deepvariant

workflow

it was Matthieu who asked, but good. I've dealt with the issue by removing the deprecated one then