As part of getting thing documented and public, I'd like to capture the status and nature of the master and dev branches of this repo here in the README.
To that end, I'd like to explicitly list the nature and care of these two branches. For example, I'd want to be able to write something like:
master
direct addition of new and modified models from noctua (every half hour)
overlay of the contents of syngo-go-cams master (update frequency TBD, currently manual)
overlay of reactome-go-cams master (update frequency TBD, currently manual)
dev
based on the contents of master (manual)
overlay of the contents of syngo-go-cams master (manual)
overlay of reactome-go-cams master (manual)
test models from XYZ
test models from ABC
I believe that there are items in noctua-model dev that are used that we probably want to capture in a repo. E.g. models for ShEx testing or form testing. We should move those to a new repo (or repos) of the form BLAHBLAH-go-cams so that they can be controlled properly and documented here.
As well, we have a set of mysterious untracked files that exist on the noctua-dev server that have not been formally checked in to noctua-models dev: https://gist.github.com/kltm/cdc249ea9084dbc5981257a6ee3a7e77 . Some of those may be of interest.
The endpoint here would be to have a mechanical SOP to reset or update the useful contents of master and dev using this repo and other repos exclusively.
As part of getting thing documented and public, I'd like to capture the status and nature of the
masteranddevbranches of this repo here in the README.To that end, I'd like to explicitly list the nature and care of these two branches. For example, I'd want to be able to write something like:
mastermaster(update frequency TBD, currently manual)master(update frequency TBD, currently manual)devmaster(manual)master(manual)master(manual)I believe that there are items in noctua-model
devthat are used that we probably want to capture in a repo. E.g. models for ShEx testing or form testing. We should move those to a new repo (or repos) of the form BLAHBLAH-go-cams so that they can be controlled properly and documented here.As well, we have a set of mysterious untracked files that exist on the noctua-dev server that have not been formally checked in to noctua-models
dev: https://gist.github.com/kltm/cdc249ea9084dbc5981257a6ee3a7e77 . Some of those may be of interest.The endpoint here would be to have a mechanical SOP to reset or update the useful contents of
masteranddevusing this repo and other repos exclusively.Tagging: @dustine32 @sierra-moxon @vanaukenk @ukemi
Also see: https://github.com/geneontology/reactome-go-cams/issues/1