fix(docs): scope fenced code language linting#965
Merged
Conversation
7 tasks
|
🌿 Preview your docs: https://nvidia-preview-pr-965.docs.buildwithfern.com/openshell |
johntmyers
approved these changes
Apr 24, 2026
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
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.
Summary
Configure Markdown linting so bare fenced code blocks are allowed in internal docs while published docs under
docs/still require a language.This keeps architecture and planning documents free to use bare fences for diagrams and terminal sketches, while preserving stricter rendering/copy behavior for user-facing Fern docs.
Example
Bare fence (no type). This is now allowed in internal docs.
Fence with a type.
Changes
MD040in the root markdownlint config.MD040indocs/.markdownlint-cli2.jsonc.Testing
mise run markdown:lint:mdpassesdocs/still failsMD040Checklist