Open ccoVeille opened 4 months ago
thx for recommand. I write a testifylint.yaml job , and run the actions for top 1k github golang repo. you can check the output https://github.com/alingse/go-linter-runner/issues/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.
hi!
sorry, I did not catch how to use the project and what actions are expected from me as an author
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
But maybe https://github.com/alingse/go-linter-runner/issues/4 needs to be addressed before we could use it the way I think
The result are starting to flow see https://github.com/alingse/go-linter-runner/issues/2
I created this for a bigger readability https://github.com/Antonboom/testifylint/discussions/159
I discovered this project yesterday
https://github.com/alingse/go-linter-runner (hi @alingse :wave: )
@alingse popped out an issue on a repository I'm watching https://github.com/montanaflynn/stats/issues/84
@Antonboom I know you often look for regression/changes when working on testifylint
Examples:
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