-
Notifications
You must be signed in to change notification settings - Fork 44
How to make a new release
Mihail Anton edited this page Jul 6, 2023
·
3 revisions
-
Start a PR from develop to main with following messages
- List PRs from the previous release until now in a descending order (latest PR first)
- Specify the PR type (Features, Fixes, Style, or mixes) and associate with corresponding issue
- Briefly describe the changes but with enough details
-
Merge develop into main by accepting all changes using following commands:
git checkout main
git pull
git merge -Xtheirs develop -m "Human 1.7" (replace 1.7 with the version that should be made)
git push -
Run gene essentiality with DepMap, following the instructions in the Human-GEM-guide.
-
Create new release after merging
- Go to local
Human-GEM
folder and change to main branch - Run increaseHumanGEMVersion function with agreed type (
major
,minor
orpatch
) - Before running, better sync Cobra and Raven to the latest version
- Modify the numbers of rxns, mets and genes in
README.md
file - Commit the changes with message “chore: new version”
- Usually eight files are updated in this commit: 5 model files +
dependencies.txt
,README.md
,version.txt
- Go to local
- Introduction
- Curation guidelines