Append STRchive version number to files downloaded from /loci#downloads

[hdashnow]

Currently, downloaded files look like this:

hg19.STRchive-disease-loci.TRGT.BFiBXWeD.bed

Would it be possible to append the current STRling version number to the filename so that users can keep track of file versions down the track? For example:

hg19.STRchive-disease-loci.v2.0.2.TRGT.bed (open to format suggestions)

I'd also want to generate something similar for all the files, including json, to attach to the release. I've just been doing this manually. For example:
https://github.com/dashnowlab/STRchive/releases/tag/v1.2.0

[vincerubinetti]

Partially closed by #100

As for the releases, for now you can continue to do it manually, but you can also write GitHub Actions workflows to automate releases. For example, we could have a workflow that runs any time a PR is merged into main, and if the version number in CITATION.cff is increased, we automatically create a new tag and release, and attach files (renamed to include version string).

As for file naming convention, I think these names are a bit hard to read, especially with the repeated use of periods. If someone were to try to write code to parse out the parts, it'd also be a challenge. If you're open to changing the file names, I'd recommend something like this:

STRchive-disease-loci_v1.2.0_hg19_TRGT.bed

So it's in order of increasing specificity... Starting with the project as a whole, then the project version, etc., with big "parts" always separated with underscores .

[hdashnow]

Looks great! That works for me. I'd definitely be interested in automating this in the future. Will keep this open as a reminder.

[vincerubinetti]

The remainder of the issue, the CI, has been added to #59 to be tracked.