Final publish extended

[maxulysse]

Complement #53

Idea is:

1 genome build can have more than a single gff.

ie Human GRCh38.
The fasta is the same, but the gff is more and more refined, so the indexes of the aligners that depends on this gff are now stored in a dedicated folder.

Any alternate proposal?

PR checklist

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the pipeline conventions in the contribution docs
• If necessary, also make a PR on the nf-core/references branch on the nf-core/test-datasets repository.
• Make sure your code lints (nf-core pipelines lint).
• Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
• Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
• Usage Documentation in docs/usage.md is updated.
• Output Documentation in docs/output.md is updated.
• CHANGELOG.md is updated.
• README.md is updated (including new tool citations and authors/contributors).

[maxulysse]

I'm thinking it would be better to add source_gff as metadata in the assets.
But the publishing makes more sense this way

[adamrtalbot]

We should try and pre-populate the source GFF field, rather than using a custom string. That way, we can get the source_gff for free, no user interaction required.

Still, not blocking. This is a nice feature to add later.

[adamrtalbot]

In the pipeline, do you add the name of the GFF to the meta map? This way we get this field populated by default:

meta = meta + [ "source_gff": ${gff.simpleName} ]