You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have all astro files & assets managed via CI, we should extend that to the linkml parts of this repo's workflow.
The CI to build the framework.regen.network website should likely include:
makefile for managing generation of various artifacts
make task for generating linkml docs (from .yaml files)
make task for generating linkml taxonomy schemas (sourcing from taxonomy terms' .md files)
make task for generating JSON-LD documents for any example datasets
(4) should likely still be triggered and updated manually, with example documents checked in via version-control (it's nice to have JSON-LD docs to review when reviewing schemas)
(2) & (3) maybe should be run in CI, or as part of the cloud flare deploy together with astro's build process
while artifacts from (2) can possibly be excluded from being checked-in to source code, we probably still want to have artifacts from (3) checked-in to source code so that the linkml .yaml files are exhaustive and represent the totality of the schema including taxonomic terms
The text was updated successfully, but these errors were encountered:
We already have all astro files & assets managed via CI, we should extend that to the linkml parts of this repo's workflow.
The CI to build the framework.regen.network website should likely include:
.yaml
files).md
files).yaml
files are exhaustive and represent the totality of the schema including taxonomic termsThe text was updated successfully, but these errors were encountered: