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
It might be most convenient to set this up as a development branch that is autogenerated at either regular intervals or whenever the Google Sheets document changes. We could add this development version to the website using Mike (see cancerDHC/ccdhmodel#15).
Before we tackle this, I think it's important to identify the actual requirements from the other CRDC-H teams: do we expect to support the Google Sheets to LinkML generation process for several more months, or do we expect that they'll transition to using the YAML file directly in the next few weeks? If the latter, will the be comfortable generating the artifacts locally, or would they like us to do that in the PR as part of the development process?
The text was updated successfully, but these errors were encountered:
Just making a note on this issue with a link to this post. The post describes how we can setup the google_api_credentials.json and .env credential files so Github Actions can use it when it's trying to run the sheet2linkml CLI.
It might be most convenient to set this up as a
development
branch that is autogenerated at either regular intervals or whenever the Google Sheets document changes. We could add this development version to the website using Mike (see cancerDHC/ccdhmodel#15).Before we tackle this, I think it's important to identify the actual requirements from the other CRDC-H teams: do we expect to support the Google Sheets to LinkML generation process for several more months, or do we expect that they'll transition to using the YAML file directly in the next few weeks? If the latter, will the be comfortable generating the artifacts locally, or would they like us to do that in the PR as part of the development process?
The text was updated successfully, but these errors were encountered: