Maxime U Garcia

can you try: ``` nextflow pull hello ```

Can you do: ``` ls -l ~/.nextflow/assets/nextflow-io/hello ``` and if you have something: ``` cd ~/.nextflow/assets/nextflow-io/hello git status ``` and copy paste the results

I'd love to see that, but for the moment, `master` is still hardcoded in a lot of places. It's on our TODO list, definitively, and I'm quite adamant on having...

Same issue in the README: (there's a space missing towards the end of the line here: https://github.com/nf-core/isoseq/blob/dev/README.md?plain=1#L29)

I like this idea Is there a way to scrape the meta.yml files to update this codeowner file via a github action for example?

@Emiller88 where are we with that PR? Shall we close it?

@matthdsm Can you list the failed subworkflows in an issue, so we know which one we need to update?

Pretty sure I did not removed the labels, something weird happened there...

You mean one like that: https://zenodo.org/badge/latestdoi/54024046 That's the one you can get with the first release with Zenodo. But there's way to reserve a DOI so it should be usable...

I managed to find a solution (not as clean as I would have hoped). https://github.com/nf-core/sarek/blob/a7679b9b5c178351b1e96a3ffe7ee81ddf9aad06/main.nf#L226 Which I later use in a clean manner in a process: https://github.com/nf-core/sarek/blob/dsl2/modules/nf-core/software/qualimap_bamqc.nf