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

nf-core

to agree on the naming, 2 details:
• I have changed `lock file` to `lock_file` 
• Do we want to change `linux/amd64` to `linux_amd64` ?

I agree on the first one, but why change how we name the platform?
This seems to be inconsistent with how platforms are referred to in other tools, e.g. wave:
```$ wave --conda-file modules/nf-core/fastqc/environment.yml --platform linux_amd64 -o yaml
Unsupported container platform: 'linux_amd64'```


it was to avoid having special characters

I was mostly thinking about the Nextflow config profile names, for consistency

Mind you, we just call them `_arm` or not, so totally different

Only place I can find `linux_amd64` is in the blog post we wrote for the suggested meta spec :sweat_smile:

I guess because I also dislike slashes in stuff

This was about the meta.yml, but I think we settled on snake case everywhere in the meta.yml, didn't we?

yes, after some discussion during the infrastructure meeting we agreed to keep snake_case for consistency with other meta.yml keys