Allow multiple working directories in single action run

[nikandfor]

Welcome

• Yes, I understand that the GitHub action repository is not the repository of golangci-lint itself.
• Yes, I've searched similar issues on GitHub and didn't find any.

Your feature request related to a problem? Please describe.

It's pretty inefficient to checkout the repo multiple times with matrix if you have multiple modules and want to run linter for all of them.

Describe the solution you'd like.

Allow setting multiple working-directories like it's done for tags, platforms, and others in docker/build-push-action.

Describe alternatives you've considered.

matrix works, but it's longer and less efficient. It spends more ci minutes and it spends more dev's time.

Additional context.

I haven't seen the code and haven't estimated the efforts needed for that feature. If it's not too much I think it would be nice feature to have.

[micah-cinnamon]

I would also appreciate this feature.

Although a little messy, I found what seems to be a potential workaround in the meantime if you want to both use the official golangci-lint github action, and test a monorepo without spinning up multiple jobs. If you use the golangci/golangci-lint-action in one step to lint at your first module, you can then call golangci-lint run in a subsequent step to test any other go projects in your monorepo. Essentially:

- uses: golangci/golangci-lint-action@v8
  with: 
    working-directory: first/go/module
- run: |
    cd next/go/module
    golangci-lint run