chore: update the pre-commit hooks quarterly - #110
Conversation
pre-commit.ci checks for new hook versions every week by default and opens a pull request whenever there is one, and each needs a review. Once a quarter is enough for linters and formatters, and it is what cpp-linter/cpp-linter already does. A hook can still be updated by hand with `pre-commit autoupdate` when needed. This repository had no `ci` settings, so it also gets the ones the other repositories use, which give pre-commit.ci's pull requests and commits conventional titles.
|
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: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe pre-commit configuration adds autofix and autoupdate settings. The main workflow changes the reusable pre-commit workflow reference. ChangesPre-commit CI settings
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Merge Risk: ⚪ Minimal · up to The quarterly hook-update settings and workflow references have no identified merge-blocking issue. The change is ready for normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency. Changed systems: None identified. Architecture concerns Review detailsBefore / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
satisfies new zizmor lint
pre-commit.ci checks for new hook versions every week by default and
opens a pull request whenever there is one, and each needs a review.
Once a quarter is enough for linters and formatters, and it is what
cpp-linter/cpp-linter already does. A hook can still be updated by hand
with
pre-commit autoupdatewhen needed.This repository had no
cisettings, so it also gets the ones theother repositories use, which give pre-commit.ci's pull requests and
commits conventional titles.
Summary by CodeRabbit