lint: frontmatter-aware verdict insertion - #10
Merged
Conversation
…pted YAML frontmatter Found in the field: on a memory/dashboard page that already carries YAML frontmatter, the first-run insertion landed inside the frontmatter block and broke its parse. Insert after the closing --- instead. Claude-Session: https://claude.ai/code/session_013ERfM4utJGsw4McARGJt6a
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.
Follow-up to #9: the weekly lint's first-run insertion of the verdict block used a naive line-2 insert — on a memory.md that already has YAML frontmatter, the block lands inside the frontmatter and corrupts its parse (found in the field on a dashboard page). Now inserts after the closing
---.https://claude.ai/code/session_013ERfM4utJGsw4McARGJt6a