-
Notifications
You must be signed in to change notification settings - Fork 7
Editorial improvements for #672 #673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
github-actions
wants to merge
4
commits into
main
Choose a base branch
from
style/editorial-672
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
…ragraph to follow 10/20/70 structure
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
nearestnabors
approved these changes
Jan 20, 2026
nearestnabors
added a commit
that referenced
this pull request
Jan 20, 2026
LLMs often wrap their markdown output in ```mdx or ```markdown code fences, even when instructed to return only the content. This caused the editorial review workflow to commit files with spurious code fence markers at the beginning and end. Added stripCodeFences() helper that removes these markers from only the start and end of responses, preserving any legitimate code blocks within the content. Fixes issue seen in PR #673. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
nearestnabors
added a commit
that referenced
this pull request
Jan 21, 2026
LLMs often wrap their markdown output in ```mdx or ```markdown code fences, even when instructed to return only the content. This caused the editorial review workflow to commit files with spurious code fence markers at the beginning and end. Added stripCodeFences() helper that removes these markers from only the start and end of responses, preserving any legitimate code blocks within the content. Fixes issue seen in PR #673. Co-authored-by: Rachel Lee Nabors <nearestnabors@users.noreply.github.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
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.
Editorial Review
This PR contains structural improvements to documentation changed in #672.
Changes
Context
These suggestions are based on our style guide and focus on document structure, not word-level fixes (which are handled by Vale).
Review each change carefully - accept what improves the docs, modify what needs adjustment, or close this PR if the changes aren't helpful.
Generated by editorial review using Claude