Open michaelpj opened 1 year ago
Yes: https://github.com/action-works/cabal-cache-s3
But for HLS release CI this isn't enough. We use cabal-cache in the bindist-makefile, which is a bit hard to wire up with a github action.
Sure, it might not work for HLS but I think it would be nice for other people. Generally having these things as github actions works when the top-level structure of what you're dong is specified in the workflow file, which it isn't in the bindist case currently. Maybe it would be clearer in some ways if it was? Not sure.
It would be cool to have something that was a bit like the standard Github caching action.
It wouldn't be very sophisticated I expect, just something that triggers a save/restore in the right places and has some parameters for setting up the storage location, but it would still look a bit cleaner from a user perspective.