consider go-linter-runner project

[ccoVeille]

I discovered this project yesterday

https://github.com/alingse/go-linter-runner (hi @alingse 👋 )

@alingse popped out an issue on a repository I'm watching
montanaflynn/stats#84

@Antonboom I know you often look for regression/changes when working on testifylint

Examples:

• compares: shall suggest (Not)Same when comparing pointers #93 (comment)
• helpers: isError: strict type comparison instead of implementing check #97 (comment)

is this something that could be useful for you ?

are you using such a tool by yourself? or are you launching your tests on local repository like I do.

cc @mmorel-35 who might be interested

[alingse]

thx for recommand. I write a testifylint.yaml job , and run the actions for top 1k github golang repo.
you can check the output alingse/go-linter-runner#2

if you only care about the panic, I can update the includes option, you can fork or modify the repo if you would like.

[Antonboom]

hi!

sorry, I did not catch how to use the project and what actions are expected from me as an author

[ccoVeille]

hi!

sorry, I did not catch how to use the project and what actions are expected from me as an author

The tool made by @alingse can be used to launch testifylint on thousands of go projects.

So you would be able to see how things varies from one version to another, even let's say code that is currently is PR and development

[ccoVeille]

But maybe alingse/go-linter-runner#4 needs to be addressed before we could use it the way I think

[ccoVeille]

The result are starting to flow see alingse/go-linter-runner#2

I created this for a bigger readability #159