Repository navigation
ci: validate navigation, internal links, and MkDocs before wiki merge - #37
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 59a80fe1f6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Adds read-only pull_request validation. The stdlib Python validator checks all Wiki.js navigation entries, changed-page front matter and local links (with unit tests), while a separate job runs the same staging/rewriting scripts as the Pages deployment and
mkdocs build --strict. The changed-file scope intentionally avoids blocking unrelated legacy pages. Does not crawl external links. AI-assisted implementation; please review CI on this PR before making checks required.