Repository navigation
Format the README JIT example for ruff-format - #8785
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: RustPython/RustPython/.coderabbit.yml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe README removes trailing whitespace from a blank line in the JIT compiler ChangesREADME whitespace cleanup
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Merge Risk: ⚪ Minimal · up to This documentation-only formatting change has no runtime or user-facing behavior impact and is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
youknowone
changed the title
ruff-format 0.16.7 formats Python fences in Markdown and wants two blank lines after a top-level function. Assisted-by: Grok:4.6
be4c725 to
24038a2
Compare
One of checkbox below must be checked.
Summary
#8777 fails Lint because ruff-format 0.16.7 now formats Python code blocks in Markdown. The JIT snippet in README.md had one blank line after a top-level
def; the formatter wants two.Format that example so the bump can land. Do not pin the hook away from Markdown.
Assisted-by: Grok:4.6
Summary by CodeRabbit