I just noted I have a number of

conf/containers*.config

in metatdenovo that aren't read anywhere. Claude tells me they're generated from the

meta.yml

containers

block. What am I supposed to do with them?

the root nextflow.config doesn't do it?

Not yet, but I can certainly add them there if that's the way it's supposed to be. I think linting might have generated them. Also, some of them have

oras

in their names, but we're not supposed to use that, right?

🫠

OK, so I'll just leave them for now?

My guess people using these setups can point to these files

Also harmless to delete if you want to

If they were generated by linting, I suppose they will be regenerated? They don't do any harm, so I'll keep them.

Ok I just had this happen when I updated some nf-core modules, and I have to say strong dislike. They get created with no explanation or indication and create a crazy amount of bloat as a side-effect of a command you don’t expect to modify anything outside of

modules/**

. And AFAICT with the module I have updated, the

<http://main.nf|main.nf>

still has the old-style container declaration anyway.