Add a linter workflow

[dannystaple]

Linting for this code.

[Stedders]

This is a good idea, but could we use pre-commit rather than doing it this way?

I see the linter has failed, and we now have to go through the log and work out why. It would be better to highlight and fix any issues before pushing.

I'll add one to the PR and push an example.

[dannystaple]

Ah, I use precommit on some other areas.in theory megalinter fires off many linters in parallel. It is a derivative of GitHub’s superlinter. In practice it has some issues around dependencies. I’ll admit to test bedding megalinter here (having used superlinter on others).Turning on many linters at once tends to show up many things, my intention would be pick off smaller fixes and bring them in. Precommit is handy, and has plenty of linters. It does allow more incremental linter improvements that the rather blunt force of megalinter (or superlinter). Let me see about an alternative PR for getting in a simple precommit yaml (and pipeline run of it). I can follow up with other linter steps.Sent from my iPhoneOn 14 Feb 2023, at 07:38, Stedders ***@***.***> wrote: This is a good idea, but could we use pre-commit rather than doing it this way? I see the linter has failed, and we now have to go through the log and work out why. It would be better to highlight and fix any issues before pushing. I'll add one to the PR and push an example. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>