Describe how model curation is tracked and new releases are made:
[ ] Use latest_changes.py script in /code to link to most recent curation script in /code/curation, which is name with the planned release number (e.g. v1_3_0.py) (would not solve all issues, suggestion to use sys.path.append("..") in each script is better solution)
[x] Update contributing guidelines, based on yeast-GEM with some modifications
[x] Move contributing guidelines to .github folder
[x] increaseVersion.py function that should be run on master branch to prepare a new version release
[x] Include version.txt in master branch and update by increaseVersion.py
[x] Update model metrics in README.md by increaseVersion.py
[x] Replace history.rst with HISTORY.md and check by increaseVersion.py (history only present in master, not devel, as its linked to a specific release).
Describe how model curation is tracked and new releases are made:
Use(would not solve all issues, suggestion to uselatest_changes.pyscript in/codeto link to most recent curation script in/code/curation, which is name with the planned release number (e.g.v1_3_0.py)sys.path.append("..")in each script is better solution).githubfolderincreaseVersion.pyfunction that should be run onmasterbranch to prepare a new version releaseversion.txtinmasterbranch and update byincreaseVersion.pyREADME.mdbyincreaseVersion.pyhistory.rstwithHISTORY.mdand check byincreaseVersion.py(history only present inmaster, notdevel, as its linked to a specific release).