The cache action section focuses on GHES which is a shame, since the GitHub.com cache action is also pretty bad. - can't manually delete cache (although they'r

The cache action section focuses on GHES which is a shame, since the GitHub.com cache action is also pretty bad. - can't manually delete cache (although they're considering changing that[0]) - only saves cache at the end of a workflow, and only if the workflow succeeds. This could be solved with CircleCI's approach of having a save-cache step and a restore-cache step. - Cache is super slow for self-hosted runners, so it makes more sense to have a local cache instead of using the action - only 5gb of storage size. This was supposed to be increased via billable cache storage[1], but it's been on the backburner since July 2020 - In addition to the above, you can't use a different storage backend on the official action (which would allow storing over 5GB of cache via your own storage). The best workaround is to use a user-provided action which utilizes the s3 api[2]. 0: https://github.com/actions/cache/issues/632 https://github.com/actions/cache/issues/632 1: https://github.com/github/roadmap/issues/66 https://github.com/github/roadmap/issues/66 2: https://github.com/actions/cache/issues/354#issuecomment-854762521 https://github.com/actions/cache/issues/354#issuecomment-854... 2>