Live data from Hacker News

GitHub Super Linter: one linter to rule them all

github.blog

31–40 of 360 posts

Re: GitHub Super Linter: one linter to rule them all

#31
post #26

Earlier quoted context omitted.

Docker is probably the least annoying solution, would you rather install linters for 40 different languages on your system?

Install linters as needed / pick up what's already installed could be a feasible option.

Sure, if you want to get a billion issues reported that are caused by outdated versions of the linters.

Re: GitHub Super Linter: one linter to rule them all

#32
post #25

Earlier quoted context omitted.

Docker is probably the least annoying solution, would you rather install linters for 40 different languages on your system?

I'd rather not run a linux VM for this, so yes. It should be possible to isolate it to /opt/github-linter/* on my BSD machines, or put into a nix package. (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.')

[deleted]

Re: GitHub Super Linter: one linter to rule them all

#33
post #13

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-...

It's kind of odd that GitHub is asking people to pull an image from a Docker account that most people won't recognize (admiralawkbar/super-linter), as opposed to an official GitHub one.

Re: GitHub Super Linter: one linter to rule them all

#34
post #31
post #26

Earlier quoted context omitted.

Install linters as needed / pick up what's already installed could be a feasible option.

Sure, if you want to get a billion issues reported that are caused by outdated versions of the linters.

Outdated version could simply be counted as nonexistent, then a new version would be installed "as needed".

Re: GitHub Super Linter: one linter to rule them all

#36
post #33

Earlier quoted context omitted.

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

It's kind of odd that GitHub is asking people to pull an image from a Docker account that most people won't recognize (admiralawkbar/super-linter), as opposed to an official GitHub one.

Which is funny too because GitHub repos have Docker repository functionality: https://github.com/features/packages

But since its release, you still can't do public pulls: https://github.community/t/docker-pull-from-public-github-pa...

Re: GitHub Super Linter: one linter to rule them all

#37
Great! Now do it for code formatters!

After using Prettier for a few years I'm firmly in the camp of mandatory/enforced code formatters. As long as it's a half decent formatter like Prettier I believe my personal opinions on the specific formatting choices are much less important than essentially never having to think about formatting again, in particular having to ask people to fix formatting in code reviews (or fix it myself).

I also love just banging out code, saving, and having my editor clean up the formatting for me.

Re: GitHub Super Linter: one linter to rule them all

#39
post #33

Earlier quoted context omitted.

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

It's kind of odd that GitHub is asking people to pull an image from a Docker account that most people won't recognize (admiralawkbar/super-linter), as opposed to an official GitHub one.

What was Admiral Ackbar's famous quote?

Re: GitHub Super Linter: one linter to rule them all

#40

> Setting up a new repository with all the right linters for the different types of code can be time consuming and tedious. Is it? In my company I maintain a set of exemplars for all of our commonly used repository types. When someone wants to make a new one they just copy and paste stuff from one of the exemplars. Over the years I've come to value "white box" code re-use over "black box" re-use. In my experience man…

So basically you've done the same as super linter at your company. But now, nobody else has to go through the pain of setting all of the exemplars up, because you get nice defaults, everything included for free from super linter.
Post reply on HN