New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finish automation & add a GitHub Action #31
Comments
Currently, running the action will overwrite the existing |
We def. need the versioned releases asap - there should not be a Indeed, latest is managed by github: creating a versioned release is all you need to do! |
I think I did this for ease of downstream slurping. Wasn't sure if the GitHub REST API allowed you to see which one was the latest, but I know it can check for explicit tags. So the idea was that it would check the releases, find the one with the tag In the past, I've made a versioned release in addition to the one tagged I do agree it is very good if the releases are versioned automatically. However, I don't know what a good solution to this problem is: If we're using semver, there isn't really a good way for a script to know whether or not a release is a (a) major update, (b) minor update, (c) patch update. Possible solutions?
|
Github has now a Instead of semver, we can use date based versioning like in OBO: |
I'm fine with these changes. Will address when I get back to working on this issue. |
Updated issue to reflect new decision.
|
Tasks
pip install -r requirements.txt
andpython -m omim2obo
YYYY-MM-DD
.The text was updated successfully, but these errors were encountered: