Open
Description
@vkt1414 I suggest we add 2 GitHub actions:
- Daily action that checks if there is an update to the IDC release BQ tables. If update is detected, it will
- run all queries in the
queries
folder, and save the result of each query as<query_prefix>.csv.zip
in the "latest" release - make a PR to update IDC version in https://github.com/ImagingDataCommons/idc-index/blob/main/idc_index/index.py#L65.
- run all queries in the
- Commit-triggered action that will look for release tags that follow our versioning pattern. When a tag release is detected, it will:
- create a GitHub release with the release tag
- attach indices from "latest" to the new release
- trigger PyPI package release
- Commit-triggered action that will
- run all the tests
- if queries are updated, re-run and update CSV in the latest release
- PR-triggered action that will
- if queries are updated, re-run the queries first and save resulting CSV in a place accessible during tests
- run all the tests (I think for this it will be beneficial to be able to run the test with the manually configured location of the table passed via the constructor)
What do you think? Did I miss anything?
Metadata
Metadata
Assignees
Labels
No labels