Refresh the format registry gathering code and actions#23
Open
Refresh the format registry gathering code and actions#23
Conversation
anjackson
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 refresh of the Sentinel code adds in more data sources, and builds a SQLite database too. Note that this can get confusing because most of the actual code that updates the actual data sources is in the sister project https://github.com/digipres/digipres.github.io which is 'mounted' here as a submodule. So the new stuff here, mostly to do with building a SQLite version separately from the existing workflow, doesn't get run by the Sentinel GitHub Action, but updates to the submodule code do (so e.g. collecting the additional data sources etc.).
This should probably be a code module that is run from an action on the actual https://github.com/digipres/digipres.github.io repository. This would help avoid the fact that the scheduled action gets stopped every 60 days if there are no commits in here.
Note that this new workflow can be run manually on GH Actions: https://github.com/digipres/sentinel/actions/workflows/data-update.yml?query=branch%3A2024-refresh