Use --unsafe
YAML check for mkdocs.yml
#911
Merged
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.
See pre-commit/pre-commit-hooks#273
The check currently fails because we use the
!!
syntax in the currentmkdocs.yml
configuration.--unsafe
refers to the YAML compliance: it doesn't load the file, merelychecks the syntax:
https://github.com/pre-commit/pre-commit-hooks/blob/98c88b23b7ea9a42f920adc1d7c8790f39772021/README.md#check-yaml
This is still better than the current situation because:
--no-verify
or spend time trying to work out what's wrong with the pre-commit
failure
in the current broken state
In practice, this YAML file gets loaded by MkDocs, which tells us if it's broken
anyway.
Other YAML files in this repository are still checked fully.