Should this repo have a build/test/autoupdate pipeline?
nixinator opened this issue · 3 comments
These flake templates track nixpkgs-unstable , however the do have flake.lock files, which should reduce breakage going forward into the future. (where i am from).
Should the these templates be 'nix flaked update' (ed) automagically and recomitted?
Also, be a good pattern add some 'nix flake check' code too, showing new flake users best practise
Weird breakage in templates (but fixable) can be the kiss of death for new users, and send them into a spiral of confusion and despair (but maybe slightly less despair form the Operating systems they just came from). This is a little more critical if @garbas wants to put them on the nixos learn web site.
Maybe if i want nix guarantee's I should by a toaster. ( which is my nickname).
What you wrote is definitely the plan. There are many steps to get to get there, the work in #18 is just step 0.
We need to test not only if template works, but also if tutorials in README.md are working as described.
@garbas I have contributed to the current readme, and I would love to help with expanding that further. For testing nix flake init, do you think doing that in CICD would be a good idea? So that everything is automatically
What you wrote is definitely the plan. There are many steps to get to get there, the work in #18 is just step 0.
We need to test not only if template works, but also if tutorials in
README.mdare working as described.
Multiple idea: generate the README by including shell script (I don't recall but seen other project did that) or use some tool/marker to extract like https://github.com/endocode/shelldoc (frist one found)