Why can't I re-use cache created by actions/setup-go for actions/cache? about setup-go

[aparnajyothi-y]

Hello @sswastioyono18, Thank you for creating this issue and we will get back to you once we have some feedback on this :)

[gowridurgad]

Hi @sswastioyono18, The actions/setup-go does not inherently create a cache that can be reused by other actions. The cache option in actions/setup-go is specifically for speeding up the setup process by reusing a previously installed version of Go, if available. The actions/cache action, which is a separate entity, is designed for caching dependencies and build outputs to enhance the speed of the workflow. These two actions serve different functions and are used independently.

To cache Go dependencies or build outputs, actions/cache is typically employed directly in the workflow configuration. The cache created by actions/setup-go is not designed to be reused by actions/cache as it doesn't cache Go dependencies or build outputs. And It's possible to utilize the cache created by actions/cache in the main branch within a feature branch.

I hope this helps clarify the roles of these two different actions and how they can be utilized in GitHub Actions workflows.