![]() since we're not enabling _any_ auto-correct if there are still existing violations, it seems easier to enable unsafe autocorrects for new code, when you're most likely to know how to fix it. instead of getting frustrated and wondering why gergich is complaining about something that should have been auto-corrected Change-Id: Ic81316c790820e2d32a1b1826c79ccaa77d1d6ad Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/278081 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Simon Williams <simon@instructure.com> QA-Review: Cody Cutrer <cody@instructure.com> Product-Review: Cody Cutrer <cody@instructure.com> |
||
---|---|---|
.. | ||
pre-commit |