zkoppert

5 ms·

1. 1.▲
   by zkoppert 6y ago

   Checks all by default but you can set an env variable in the config to only check new code.
2. 2.▲
   by zkoppert 6y ago

   Considered that but thought the target audience might be familiar. I think your suggestion would have made it more accessible though to those who have not been around linters before.
3. 3.▲
   by zkoppert 6y ago

   Totally understand. I think the problem we are trying to solve here is integration with GitHub Actions as well being able to easily set up multiple linters for code ASR’s with many languages. Hope that makes sense.
4. 4.▲
   by zkoppert 6y ago

   Sounds like there is some consensus around switching out Standard. Feel free to open up an issue in the repo and we can discuss and move forward there if you like.
5. 5.▲
   by zkoppert 6y ago

   Yup, thats exactly what happened.
6. 6.▲
   by zkoppert 6y ago

   Thanks for sharing that! I didn't know it existed.
7. 7.▲
   by zkoppert 6y ago

   I think there is an opportunity to integrate/add your gist to the super linter. Feel free to open an issue to get that started.
8. 8.▲
   by zkoppert 6y ago

   Never thought of that! That does seem more accurate and descriptive.
9. 9.▲
   by zkoppert 6y ago

   Yes please! Feel free to open up an issue and collaborate with others to get it added! https://github.com/github/super-linter/issues
10. 10.▲
    by zkoppert 6y ago

    Hi, there is a local run option with instructions here: https://github.com/github/super-linter/blob/master/docs/run-...