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
Sometimes the gh action takes 5 minutes and then fails because of a wrong recipe format. This rating time can be avoided by adding a static checker before running everything, also users can use it locally as a githook so they never commit a wrong receipe
The text was updated successfully, but these errors were encountered:
This is planned, we'll have JSONSchema validation, the schema repo is here: https://github.com/blue-build/schema
This will also support validation inside your code editor, if it supports YAML LSP.
Since a standard comment line linking the schema is needed for LSP support, I thought that that could also encode the recipe format version: # yaml-language-server: $schema=https://schema.blue-build.org/recipe-v1.json
^ that is the line I'm using currently for testing
#180 is where we're planning recipe v2 and we'll probably roll out the schema validation at the same time as that.
Sometimes the gh action takes 5 minutes and then fails because of a wrong recipe format. This rating time can be avoided by adding a static checker before running everything, also users can use it locally as a githook so they never commit a wrong receipe
The text was updated successfully, but these errors were encountered: