Yi
@hydai No autofix sounds good to me. But if we're not running autofix, should CI report failure on lint errors?
@arujjval dannypsnl means your workflows only fix it in the workflows **without** any modifications to the code base (the PR or the reporitory). So `autofix` being `true` or `false` didn't...
@arujjval I'm wondering if we can keep `autofix: true` in `.linelint`, and use `autofix: false` in `linelint.yml`, so that when `linelint.yml` reports error, user can use your `.linelint` config directly...
I checked the source code of this action, it doesn't seem to provide input fields. It runs `linelint` like this ``` ENTRYPOINT ["/linelint", "."] ``` It's probably the same as...
I think it should be on the new repo because of #3840 if we have time to work on it.
Blocking @dependabot #3098 #3099 #3166 #3586
I think current errors came from wrong version of `clang` being used at compilation. ``` Capturing in make/cc mode... -- The CXX compiler identification is Clang 18.1.3 -- The C...
Upgraded from `0.0.347` to `0.0.354` and got the same issue here. Roll back to old versions will give: ``` ✗ No model available. Check policy enablement under GitHub Settings >...
I'm not sure if this is directly related, but in case someone encounters the same issue, I still leave it here. All of these happened to me: 1. I updated...