Repository navigation
Apply fixes by default - #166
Conversation
In practice we never use this hook without the `--fix` argument, and forgetting it in `.pre-commit-config.yaml` has only caused problems. Apply fixes by default, keep the `--fix` argument for backwards compatibility, and add a `--no-fix` argument to skip the fix step. Also fix a small issue with `verify-copyright` not being able to even display the help message if `git` is not present.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (4)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe lint command now applies fixes by default and supports ChangesFix Option Behavior
Copyright Hook Import
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Suggested reviewers: Merge Risk: ⚪ Minimal · up to The hooks now apply fixes by default, and --fix is still accepted for backwards compatibility. No merge-blocking risk was identified. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
jameslamb
left a comment
There was a problem hiding this comment.
I agree and support this, thanks.
|
/merge |
In practice we never use this hook without the
--fixargument, and forgetting it in.pre-commit-config.yamlhas only caused problems. Apply fixes by default, keep the--fixargument for backwards compatibility, and add a--no-fixargument to skip the fix step.Also fix a small issue with
verify-copyrightnot being able to even display the help message ifgitis not present.