Make sure that all templates in src/ontology/template are up to date
Make sure scdo-edit.owl is up to date. If you add scdo-edit.owl from an outside source (Web protege etc) inspect the diff carefully before committing it!
make sure to run git status to see that you have no uncommited files. Make a new branch (git check -b mycoolbranch)
run make prepare_release
If all works fine run make release
Look at scdo.owl (top level, not src/ontology) in protege. eyeball. if ok:
commit push pull request review merge
github release workflow:
Go to your releases page on GitHub by navigating to your repository, and then clicking on releases (usually on the right, for example: https://github.com/{{ project.github_org }}/{{ project.repo }}/releases. Then click "Draft new release"
As the tag version you need to choose the date on which your ontologies were build. You can find this, for example, by looking at the {{ project.id }}.obo file and check the data-version: property. The date needs to be prefixed with a v, so, for example v2020-02-06.
You can write whatever you want in the release title, but we typically write the date again. The description underneath should contain a concise list of changes or term additions.
git statusto see that you have no uncommited files. Make a new branch (git check -b mycoolbranch)make prepare_releasemake release{{ project.id }}.obofile and check thedata-version:property. The date needs to be prefixed with av, so, for examplev2020-02-06.