Updates and improvements to pre-commit config#662
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
📜 Recent review details🧰 Additional context used🔀 Multi-repo contextLinked repositories findingsFramework-R-D/action-workflow-setup
Framework-R-D/action-configure-cmake
Framework-R-D/action-complete-pr-comment
Framework-R-D/action-handle-fix-commit
No cross-repo consumers of changed APIs/types were found; the only observed overlap is shared pre-commit/tooling configuration pinned to the older versions above. 🔇 Additional comments (1)
📝 WalkthroughWalkthroughUpdates the pinned versions of three pre-commit hook repositories in ChangesPre-commit hook version updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
clang-formatcompatible with the LLVM/Clang we're usingprek auto-updateexcludingclang-format.pre-commit-config.yamlto refresh pre-commit hook repositories.rufflinter hooks in the pre-commit setup.clang-formatto a version compatible with the current LLVM/Clang toolchain.prek auto-updatewhile excluding theclang-formatrepository from that automated update.ruff-pre-commitandprettier.