Repository navigation
ci: check that every page is in the nav independently of the build engine - #16
Merged
Merged
Conversation
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
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.
Refs #13. Zensical does not enforce
validation.nav, so a page left out of the nav would go unreported after a switch.scripts/check_nav.pychecks the same rule frommkdocs.ymldirectly, in both directions:docs/**/*.mdis listed in the navIt runs in
validate.ymlanddeploy.ymlbefore the build, and inbuild.sh. The loader ignores the!!python/nametags used by the markdown extension options.Checked locally: passes on main (151 pages), fails on an added orphan page and on a nav entry pointing at a missing file.