Repository navigation
fix(validate): fail on a page file beside a directory of the same name - #102
Merged
Merged
Conversation
Loading
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.
The shape that broke
/docs/jobs/compose/*in production on 2026-09-24:jobs/compose.mdxbesidejobs/compose/. All 24 children served the parent's content. The sitemap and llms.txt listed them, so the build saw them; only the routing collapsed, andmint devdoes not reproduce it, so nothing caught it before the live site.The validator now fails on that shape and names the fix (
<dir>/index.mdx, asstorage/andautomation/already do).Verified it fires: recreating
jobs/compose.mdxmakesvalidate:navreport the violation, and removing it goes back to clean. A check that cannot fail is worse than no check.