Fix runaway code fence on the Compiling WLED page#344
Conversation
The "WLED BUILDS" fence in step 3 of Making a custom environment opens at column 0 while the surrounding list is indented, so the closing fence never matches. Everything after it (steps 4 to 8 and the Adding usermods example) renders inside one big code block. Indent the fence to the list's content level so it stays a small snippet inside step 3.
|
Warning Review limit reached
Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughChangesDocumentation formatting
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/advanced/compiling-wled.md`:
- Around line 67-71: Update the fenced code block surrounding the WLED BUILDS
platformio.ini content to specify the ini language identifier, while preserving
the block contents unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: e7c903cc-b763-4522-95d7-4a417b2eac0e
📒 Files selected for processing (1)
docs/advanced/compiling-wled.md
1 participant
The "WLED BUILDS" code fence in step 3 of Making a custom environment opens at column 0 while the list around it is indented one space, so the closing fence never matches. Everything after it (steps 4 to 8 and the Adding usermods example) currently renders inside one big code block on the live page.
This indents the fence to the list's content level, so it stays a small snippet inside step 3 and the rest of the section renders normally again. Verified with a local mkdocs build.
Summary by CodeRabbit