A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

any preferences how the conda lock files for each module should be called? I was thinking of `.conda/$arch-$buildId.txt` , e.g. `.conda/amd64-d58f60e4deb769bf_1.txt`:+1::skin-tone-2: :-1::skin-tone-2: ?

maybe `./conda-lock` to be even more explicit?

yes, see <https://github.com/nf-core/testpipeline/tree/seqera-containers-conversion-manual> (i just took the directory naming from <https://github.com/nf-core/modules/pull/5827#issuecomment-2786278791|this comment>)

should the meta.yml contain the URL or the paths to the lock files?

overarching theme being that we use wave to build, but not serve