Open
Description
Anybody welcome to help with next:
- Choose the name
- Add Cachix cache
- Get the Cachix secret
- Register Cachix profile
- Get the Cachix secret
- Commit things learned from the process of merge into HNix
- Include the Haskell Nixpkgs integration test (forgot that made this)
- Refactor the
haskell-with-nixpkgs
CI into the form that HNix arrived at - Migrate to
haskell/action
- Documentation
- Gather comments into the doc
- Make project setup as a submodule, use a branch with autorebase so it would be a downstream installer as a project submodule
In theinstall
branch rebase with deleting ourcabal
,hs
,.github
, and patchingshell.nix
to use../.
should be enough.
We can even construct the installer test, use our own project or third-party project, add submodule to it, go into submodule and do the Nix-shell testing. - Add Nixpkgs static executable build to CI
- Add Complettioins test
- Add Executable
- Look into GitHub CI updates, its infrastructure is cumbersome:
- Try to find ways to condense it (share envs/patterns between workflows/builds).
- Is there is a way to use other paths then
/.github/
- It would allow for a submodule.