Repository navigation
fix: escape angle brackets in agent notes so the docs build - #433
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
1 participant
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.
Fixes the
Deploy docsfailure on main:docs/agents.md:594aborted the VitePress build with "Element is missing end tag".scripts/generate-agents-docs.jsinjecteda.notesinto markdown unescaped, and several notes carry literal paths — `~/.zcode/skills//SKILL.md`, `/.agents/skills`. VitePress reads a bare `<...>` in a `.md` file as a Vue tag; the unclosed one killed the whole build. The wording was incidental — any future note with an angle bracket would have broken it the same way — so the generator escapes instead.No CI ran this: `Deploy docs` only builds on push to main, so the failure landed after merge rather than on the PR. A test now asserts the generated Notes section contains no bare
<.