Automatic release based on tags

[napulen]

The idea of this gh-actions workflow is very simple:

Every time a new tag is created, the script will

• Pack the contents of the Corpus folder in a zip file
• Pack the full contents of the repository (minus version history)
• Create a release that will include those Zip files in the main Releases section of the repo

It is a very simple idea but I think very powerful and sustainable.

On the side of the developer, this is what needs to be done:

• Develop as usual (commit code/music, assess pull requests, etc.)
• Once a desirable state has been achieved on the repo, worthy of a new release, do the following

$ git tag vX.Y
$ git push origin --tags

And that's it. vX.Y of the dataset will be publicly available, and a .zip file for the repository (or only the Corpus) will be created and freely available to the public.

If additional steps are necessary (e.g., also push the Code repository on its own zip file), the .yml script should be easily adaptable.

[MarkGotham]

Great, thanks! Merging and testing now.