release pipeline/script

description

For triggering a release there could be a script/pipeline that takes emg-edit.owl, with updated version info as an input, copies and renames the files, adds the version info into the new emg.owl and then triggers the creation of the HTML generation. The HTML files should be stored in the repo in a "HTML deployment" branch in order to be easily pulled to the deployment container.

ToDo's

the initial list of to do's from my point of view:

• generate script for release
• create way to parse user-defined input (i..e as input argument for python file / via yaml file)
• rearrange files and add semantic version info to owl files for release
• trigger WIDOCO and generate HTML documentation
• save documentation into repo on separate branch