Tagging the published ontology version

flora-phenotype-ontology / flopoontology

Scripts, data files and ontologies for the FLOPO project

http://flora-phenotype-ontology.github.io/

BSD 3-Clause "New" or "Revised" License

9 stars 4 forks source link

Tagging the published ontology version #7

Open rvosa opened 8 years ago

rvosa commented 8 years ago

To make things easier for readers of the FLOPO manuscript it would be convenient if there were a tagged release that uses semantic versioning (e.g. v0.1.0). Barring that and/or for the time being, it is worth noting that the version in the manuscript corresponds with revision e0e1450b91d12a9990338c1030d0cb190cc6ef9e

rvosa commented 8 years ago

In the interest of completeness: this can be done like so:

$ git tag -a v0.1.0 e0e1450 -m "Manuscript version" $ git push --tags origin master

I notice that the repository is now also linked to Zenodo so if that is configured correctly this tagging will also trigger the minting of a DOI.