-
Notifications
You must be signed in to change notification settings - Fork 6
GitHub actions
To run one of the actions that can be triggered by a user:
video.mov
This action is ran at every push and is the quality control from OBO.
This action has to be triggered by a user and creates a new draft release, more info in the release docs.
This action is ran automatically on pull request, and creates a comment in the pull request describing the differences that have been added to the ontology. An example comment can be found here. You have to click on Click to expand
to show the content.
This action has to be triggered by a user and updates the local import files if:
- There have been changes to imported ontologies (e.g. if there have been changes in CHEBI, the import files may change).
- New terms have been added to the
.txt
files insrc/ontology/imports
. See below
If you need external terms for logical definitions that are not included in the .txt
files in src/ontology/imports
, for instance, a GO term that is not in src/ontology/imports/go_terms.txt
, follow the same steps as in editing the ontology, but instead of editing in Protege, add the terms to the adequate text file.
After you have merged your pull request into master adding the terms to the .txt files, run the "Refresh imports" action on your branch. This will take around 40 mins and make a new pull request into your branch with the updated imports. Wait for the CI checks to pass on the new branch created by the action, and then merge into your own branch. Pull the changes locally, and the terms should be available in protege.