Closed ronaldtse closed 3 years ago
This issue is blocking confium.org deployment. @strogonoff can we can get it fixed up today? Thanks!
e.g. we can have workflow files namespaced for Aperis/Paneron. e.g. .github/workflows/aperis_xxx.yml, and do not delete the existing workflow files not created by Aperis? People will want to have custom workflows depending on datasets.
This is an interesting idea. I suppose we could support both dataset-specific workflows (should be easier) as well as cross-dataset (repo-wide) workflows (more involved, can be done later).
Agree.
Since an extension can not by design affect data outside the directory containing a dataset it manages, Paneron would have to provide a special hook for it to contribute a CI configuration. Tracking that in https://github.com/paneron/paneron/issues/17
Paneron alpha 19 / Aperis alpha 34 now drops CI workflow despite it being present before. Such as https://github.com/confium/confium.org/pull/1