Need a way for caching to be for entire repo; not scoped to per-branch builds

[ste00martin]

We exclusively use git tags for mobile releases, and due to the nature of tags we never gain the performance of caching because each tag is treated as a separate branch even when the tag is within the same branch.

The ask is to have an option to disable scoping caching on a per-branch basis and have the cache be for the entire shared repository - the developer would have the power to cache bust by using the cache key alone without any extra rules with this feature.

[smil2k]

@ste00martin I also wondered about having "global" cache. I definitely love to see it, I always saw it as kind of strange. As far as I know it had some security implications.

[Danand]

Second that!
Almost all of my workflows triggers on push of tag, so there is no performance gain, even the most of tags belong to the same branch main Actions cache is great feature, but ref scope is just really annoying thing now.

[pauldraper]

I don't understand why it was designed this way....there is a cache key.

If users wanted their caches scoped by branch, or tag, or commit hash, they would include that in the cache key.

[stanislas]

Can someone explain to me the security risk? I strictly only cache dependencies and the key is computed from the dependency information. All is deterministic. So I do not understand the security problem.

Update: I understand now: https://github.com/actions/cache/issues/79#issuecomment-552559765

[github-actions[bot]]

This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days.

[mjperrone]

I am still interested in support for something like this.