GitHub Super Linter: one linter to rule them all
1–10 of 360 posts
Re: GitHub Super Linter: one linter to rule them all
#2Re: GitHub Super Linter: one linter to rule them all
#3Re: GitHub Super Linter: one linter to rule them all
#4Perhaps it would have been better pitched a Lint-runner for CI jobs rather than a real linter.
Re: GitHub Super Linter: one linter to rule them all
#5Re: GitHub Super Linter: one linter to rule them all
#6I wish this would also prevent creating PRs that don’t pass the lint rules. It reduces churn on PR reviewers.
Re: GitHub Super Linter: one linter to rule them all
#7I 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...
Re: GitHub Super Linter: one linter to rule them all
#8The Perl validation seems to be restricted to "compile with warnings", despite "perlcritic" being now almost 15 years old, predating both some other linters' and even some other languages' very existence.
I'll try to see how feasible it'd be to add it as a ("the"?) Perl linter to be used as using just the compilation step to infer everything's fine doesn't really satisfy the role a linter is meant to have.
Re: GitHub Super Linter: one linter to rule them all
#9[flagged]