21–30 of 360 posts
So, this looks interesting. Rather than a real new linter, Github is proposing a tool that runs against a number of common linting standards with a single shared standard library. Perhaps it would have been better pitched a Lint-runner for CI jobs rather than a real linter.
Earlier quoted context omitted.
Hi, there is a local run option with instructions here: https://github.com/github/super-linter/blob/master/docs/run-...
Have to install docker to run a linter... Nah, thanks.
A problem I can see with this super linter is that it seems be written exclusively for GitHub Actions; there's no local install option. (I didn't read the code, maybe you can use lib/linter.sh directly, but it's certainly not directly supported.) So contributors have to rely on the CI feedback loop to see if their changes are compliant (insert fencing comic here)... Or more realistically, still use whatever linters t…
Hi, there is a local run option with instructions here: https://github.com/github/super-linter/blob/master/docs/run-...
Having to use docker certainly affirms "I get why it's probably not ideal as a local tool" to some extent, though...
Earlier quoted context omitted.
Have to install docker to run a linter... Nah, thanks.
Docker is probably the least annoying solution, would you rather install linters for 40 different languages on your system?
(Also, I guess this is one more reason that docker is a big red flag for 'hastily hacked together unportable software that would be hell to ship.')
Earlier quoted context omitted.
Have to install docker to run a linter... Nah, thanks.
Docker is probably the least annoying solution, would you rather install linters for 40 different languages on your system?
This is great, but desperately needs a way to also fix these issues. And all functionality should run locally as well. I imagine the latter is possible thanks to it being a docker image. So far I've been using this script I built for similar purposes: https://gist.github.com/silviogutierrez/3dca60a6b5b8fe214052... Runs locally, and only on changed files against master. Fixes all my python, JS, yaml, terraform, etc. A…
I wish this would also prevent creating PRs that don’t pass the lint rules. It reduces churn on PR reviewers.
I like the way it improves the quality of deploys. Actually different approach but same aim is hidden behind Assistant extension to Visual Studio Code. I think both solutions are complementary to improve quality of team work. If you want to check Assistant out version 0.9.0 was just released two days ago: https://marketplace.visualstudio.com/items?itemName=tomasz-s...