Once you push changes to Github, OnToology will do the below for each changed ontology
The configuation file is per ontology (a repository can has multiple ontologies). It will be created automatically if it does not exist. It is used to enable/disable the generation of documentation, diagrams and/or evaluation.The configuration file has three sections, "widoco", "ar2dtool" and "oops", for documentation, diagrams and evaluation, respectivly. Each of the sections has a key called "enable" and can has the values "true" or "false".
A sample configuration file
It generates documentation, diagrams and evaluation report for your ontologies. It also creates an issue in Github with evaluation summary.Once you register your repository OnToology will track your ontologies (in the registered repository) for changes. Whenever a change in an ontology is pushed, OnToology will generate documentation, diagrams and evaluation report for the changed ontologies. After that, OnToology will create a pull request with the generated files. You can enable/disable documentation, visualization or/and evaluation via a configuration file.
OnToology will create a folder named "OnToology" in the top level. Inside this folder, in will create the same structure of the repository. Inside the folder that is named after ontology file, there will be three folders, "documentation", "diagrams" and "evaluation". There will be configuration file "OnToology.cfg" beside these folders.
An example of a repository before OnToology is triggered
After OnToology is triggered
OnToology will ask for permission depends on the added repository, if the added repository is public, then it will ask permission to access public info, and if the added reposity is private, then it will ask permission to access private information. Also note that OnToology does not store/keep access tokens, it askes permission from GitHub everytime.