Hazel Weakly

That all looks correct to me. It shouldn't matter how you import sources, either through an overlay or directly. All the overlay does (in this particular example) is let you...

I end up setting up every repo I use `niv` in using an interesting method. I originally took inspiration for it from @nmattia's homies and have taken small ideas from...

> (One small rant: importing `nixpkgs` is pretty non-trivial (it has a lot of significant arguments), and the number of things that do it wrong (e.g. not passing `system` as...

@iandunn I'm not sure that doing that is the best solution. The problem here is that all forms are treated uniformly, including those that do not modify the configuration file...

Will this particular issue be fixed by Automattic/wp-super-cache#563?

`useState` is actually implemented in react using [useReducer](https://github.com/facebook/react/blob/c21c41ecfad46de0a718d059374e48d13cf08ced/packages/react-dom/src/server/ReactPartialRendererHooks.js#L244). The default reducer in this case is just `(state, action) => typeof action === 'function' ? action(state) : action;` So it seems...

As for some new ideas I've had... It should be well within the scope of the `haskell/actions` repo to have a separate action that is a container action. The container...

Try replacing `actions/setup-haskell@v1` with `haskell/actions/setup@v1`. I do really wish I had been able to add a migration warning before the actions repo archived the old haskell action... I've been bit...

Yes. The idea is that the tags should work like semver. In practice, you should be able to set the action at `v1` forever and not worry about it. The...

I went with one repo because it's been pretty rare in my experience that one needs to introduce backwards incompatibility into a github action. It's usually easy enough to preserve...