Repository navigation
fix(explore): quote frontmatter description to fix Hugo build failure - #1593
Merged
Merged
Conversation
Commit c5157b6 introduced an unquoted colon-space in the description value ("...knowledge graph: tutorials..."), which YAML parses as a nested mapping, breaking the Hugo build: failed to unmarshal YAML: mapping values are not allowed in this context Quoting the string makes it robust against colons and other punctuation.
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.
Problem
The content rebuild is failing at the Build Hugo site step:
(failing run)
Root cause
Commit c5157b6 ("Update _index.md explore") changed the
descriptionfrontmatter to an unquoted string containing a colon-space:In YAML,
:(colon + space) inside an unquoted scalar is interpreted as a nested mapping key, which is illegal in that position — hence the parse error. Hugo reports it at the frontmatter offset (line 2).Fix
Wrap the description value in double quotes so the colon is treated as literal text. Robust against colons and other punctuation.
Verified the frontmatter now parses cleanly as a single string.