Add GitHub action for releasing

[sbesson]

Create minimal templates ZIP archive containing the txt files for submitters only as per #13 (comment)

The outcome of this GitHub action can be reviewed https://github.com/sbesson/idr0000-lastname-example/releases/tag/v1.0.0

Two open questions:

• vx.y.z was used as a tag for the prototype but calendar-based tag or else could be considered
• the archive was called templates.zip but might be renamed or additional text could be customized if we wanted to point people at https://github.com/sbesson/idr0000-lastname-example/releases/latest/

/cc @pwalczysko @francesw

[manics]

I think either a calendar based tag or just a major version only (e.g. v1) makes more sense than semantic versioning.

Are you planning to provide submitters with a direct URL to the zip (fine as is), or to the release page (would be nice to add some body text to actions/create-release)?

[sbesson]

I was looking into ways to link to a latest release asset but it looks the only options is to link to the latest release.
That probably means we need to go the second option i.e. pointing to https://github.com/IDR/idr0000-lastname-example/releases/latest/ canonically and having a nice body of text explaining about the templates.

Maybe https://github.com/IDR/idr0000-lastname-example/blob/master/README.txt should become this body of text? I defer to @francesw for what is the most suitable for submitters.

[sbesson]

Following this morning discussion, pushed a few commits to create two sets of templates: one for HCS submission and one for non-HCS - see zip files at https://github.com/sbesson/idr0000-lastname-example/releases/tag/v1.0.5 @francesw.

[francesw]

HCS and experiment template zips look fine.

[sbesson]

Discussed back in December, I am now unconvinced this is a substantial improvement from our current statu-quo where we are pointing submitters to the archive of the full repository.

Probably something worth exploring is some tooling to generate template metadata files based on a combination of:

• type of study (screens, experiments or both)
• type of annotations (organism, genes, compounds...)