feat: improve support for multi-module repos

[dolmen]

Description:
Add support for caching dependencies for repositories made of multiple Go modules.

Example:

• Repo dolmen-go/mylogin-driver has Go modules github.com/dolmen-go/mylogin-driver and github.com/dolmen-go/mylogin-driver/cmd/mylogin-query

Justification:
Each Go module has its own set of dependencies. Dependencies caching should cover the union of the dependencies of all Go modules of the repo.

From the documentation, it looks like a single Go module is supported.

Are you willing to submit a PR?
No. I'm not familiar with GitHub Actions development.

[AnatolyRugalev]

Oh wow, I am fighting exactly this right now. I think adding working-directory option will solve this issue for me

[dsame]

Hello @dolmen, thanks for the suggestion, we are starting to investigate it

[dolmen]

Design idea: allow to pass an array of paths for the cache-dependency-path option as an alternative to a string.

Or better: automatically process all go.sum files in the repo.

[dsame]

This feature resembles actions/setup-node#735

[dsame]

Hello @dolmen ,

cache-dependency-path accepts both list and glob syntax:

          cache-dependency-path: |
             hello/go.sum 
             greeting/go.sum

          cache-dependency-path: "**/*.sum"

Sample workflow: https://github.com/akv-demo/test-setup-go/blob/cache-multi/.github/workflows/blank.yml
Sample build: https://github.com/akv-demo/test-setup-go/actions/runs/5799499947/job/15719631207

Did this answer help?

[dolmen]

Not yet tested, but it seems to fit my need.

However, what about making **/go.sum the default?

[dsame]

@dolmen i do not think it is good idea to allow implicit dependencies. I believe the user of the action should have clear understanding of where the dependencies come from.

[dsame]

@dolmen i am going to close the issue because the problem is resolved without the implementing requested feature, but please feel free to reopen it or create new one in case if the problem still exists

[artemgavrilov]

Hi @dsame , how about make documentation regarding this a little bit more clear?
#417