Sergey Vilgelm

The workaround is creating a step for every project and using the `working-directory` parameter: ```yaml golangci: name: lint runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Check golangci-lint for pkgA...

the action creates the comments, open the pull request changes page and you will see all issues. also the action does not allow overriding the format. If you want to...

Actually you don't need to use the action on second run. You can call `golangci-lint` directly: ```yaml jobs: lint: runs-on: ubuntu-20.04 steps: - uses: actions/checkout@v3 - uses: actions/setup-go@v3 with: go-version:...

Could you please use the latest version that we released yesterday? One issue with caching was resolved. ``` - name: lint uses: golangci/golangci-lint-action@v3 with: version: latest ```

I solved this issue by running the linter two times: 1. GitHub action, it will install the linter and report the issues as annotations 2. simple step with `run: golangci-lint...

@ldez this is not a bug, it is a limitation of the output format, probably we can allow to define multiple output formats

PR is always welcome

It really depends on the number of enabled linters. Some linters requires whole project to be loaded, other linters are just slow by their nature. I would recommend to add...

Does anyone know how to install python-debug on macOS?

I have played with the generics and created a small lib for openapi v3.1 https://github.com/sv-tools/openapi Feel free to use it as an example