Parametrization of CI to avoid hard-coded values #41
Description
If further extensions of the CI system for the project are to be developed, I think it would be a good idea to parametrize some of the values in the actions, as it will help with testing the workflows, as well as avoid "whoops" moments when opening pull requests. Ideally, all of the CI workflows could be successfully ran on forks of the repository, assuming all the other necessary repos are forked as well (and secrets populated).
For example, instead of cloning the opencs-ontology/opencs.github.io repo, we could clone ${{ github.repository_owner }}/opencs.github.io.
This shouldn't be too difficult with the OpenCS github.io page but might be trickier in the case of the ci-worker, as some variables are not allowed in that part of the workflow definition.
Docs for gh action contexts: https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
If this were to be implemented, hopefully issues like these wouldn't happen #39 #37.