Hazel Weakly
Hazel Weakly
The squash & merge option has broken preserving contributing commits to PR authors (off and on). I believe it currently makes me the main contributor and fails to show the...
This has actually come up before. At the time, the runner was correctly synced with the latest version of cabal, so there was no runtime hit to install it and...
Glad to hear it! I'll implement that and have it merged in after the `cache: true` PR gets merged.
It is not actually a prerequisite. At the time, the PR wasn't stalled and I didn't want to cause a lot of churn work. But, well, here we are :)...
The current best practice in order to get the cache behaving most efficient with cabal is to cache everything by utilizing `cabal-cache` rather than the native caching mechanism (but the...
To answer the original question at the top, I'd be perfectly happy to expand out the examples and include something very similar to yours. I plan to eventually have an...
I've gotta say, I truly appreciate your ability to run headfirst into every corner case known to man. It's quite the talent :) Running cabal update has been left in...
I like it so far! If we're going to have a generic `cache: true` option, it should work for stack as well as cabal out of the box. For stack,...
> How we would adopt the usage of it. The long story short is that this repo was designed to be a "monorepo" of actions. So having a directory in...
I already have to modify the windows cabal config to set the `store-dir` so I'm very open to adding the `extra-*` dirs required to get msys2 working correctly. I checked...