create ga for release management #18
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fedorov
requested changes
Nov 28, 2023
| print("No updates were found.") | ||
|
|
||
|
|
||
| # Create a new branch |
There was a problem hiding this comment.
I would think this code should only be invoked when changes were detected, no?
|
I closed PR 18 by addressing the changes requested and created a new one |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This workflow will address task 1 of ImagingDataCommons/idc-index-data#2
It will get the current version of IDC referenced in the index and check if it is outdated wrt to the IDC release referenced by the
bigquery-public-data.idc_current.dicom_allview in bigquery. If it is outdated, it will update the version in each of the queries in the queries/ folder of the repo, run them using bigquery, and generate a {query_file_prefix}.csv.zip for each query. It will also update the version in index.py.It then deletes the 'latest' tagged release if present already creates a new release with the 'latest' tag, and uploads the csv.zip files as a release attachment along with an updated query in the 'body' of the release.
Lastly, it will create a pull request to update the SQL queries in the queries/ folder and the index.py
Note: We must create a GitHub secret called SERVICE_ACCOUNT_KEY