-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add an action to validate updates to hub config files #9
Comments
I can give this a shot. I had initially thought this was completed in b59f6bc, but now I understand that doesn't validate the config files, so this action would be, in a sense, validating the validators. I'm going to implement an action that will use As a side note: I believe a workflow like this would have prevented the config errors I was getting in hubverse-org/hubDocs#152
|
Sorry I should have added more detail in the request! Yes the config is checked during submission validation but that's only triggered when model output or metadata files are submitted. It would be nice to have a workflow that is triggered by changes to the config. The hubValidations check function, as you noted, actually only wraps a This returns There's also function |
currently testing things out in https://github.com/zkamvar/example-simple-forecast-hub/actions/runs/10201766462/job/28224400302?pr=1 |
Okay, I've got something working here: zkamvar/example-complex-forecast-hub#1 (because I'm going to delete my fork, it looks like this:) ❌ Invalid ConfigurationThe schema in
|
this would make me feel better about things when i'm making updates to config files
The text was updated successfully, but these errors were encountered: