Repository navigation
feat: Quaternion based vneinteraction and vnescene integration - #45
Conversation
…d usability - Enhanced the script to recursively find C/C++ source files in specified folders, including a new option to format all CI directories. - Improved usage instructions and examples for clarity. - Added functionality to check for the availability of clang-format-17, with a fallback to clang-format. - Updated the formatting command to provide clearer output during dry runs and in-place formatting. - Refined error handling and output messages for better user experience.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 32 minutes and 49 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s clang_formatter.py helper to better mirror CI-style formatting checks by adding recursive folder discovery, an all mode targeting CI directories, and improved user messaging.
Changes:
- Make source discovery recursive and add an
all/citarget that formatssrc/,include/,samples/, andtests/. - Add clang-format binary selection logic (preferring
clang-format-17) and more explicit dry-run vs in-place output. - Refine CLI usage/help text and error messaging.
Description
Release notes: Use a Conventional Commits–style PR title (e.g.
feat: add X,fix: resolve Y,docs: update Z) so release-please can include this change in the changelog. If you squash-merge, use the PR title as the commit message.Checklist
cmake -B buildandcmake --build build, or platform script).ctest --test-dir buildor script-a test).clang-formatas configured for this repo); CI clang-format will check.Additional notes