ark/doc
Timothy DeHerrera 95c6ee0368
nix: fix #126
* Update the readme to pull from cachix first, so users don't have to
  build nix.
* Pull `nixFlakes` from override for slightly newer ui, and consistency
  for users who change the nixos flake ref to something newer.
2021-02-17 14:15:43 -07:00
..
flk doc: finish flk reference 2021-02-14 17:41:15 -07:00
integrations doc: usage for deploy-rs 2021-02-15 11:08:17 -07:00
start nix: fix #126 2021-02-17 14:15:43 -07:00
.gitignore doc: new mdbook documentation 2021-02-14 02:46:05 -07:00
CONTRIBUTING.md doc: finish flk reference 2021-02-14 17:41:15 -07:00
layout.md doc: new mdbook documentation 2021-02-14 02:46:05 -07:00
README.md doc: finish flk reference 2021-02-14 17:41:15 -07:00

Pull Requests

If making a change to core, or adding a feature, please be sure to update the relevant docs. Each directory contains its own README.md, which will automatically be pulled into the mdbook. The book is rendered on every change, so the docs should always be up to date.

Community PRs

While much of your work in this template may be idiosyncratic in nature. Anything that might be generally useful to the broader NixOS community can be synced to the community branch to provide a host of useful NixOS configurations available "out of the box".

Style

If you wish to contribute please follow these guidelines:

  • format your code with nixpkgs-fmt. The default devshell includes a pre-commit hook that does this for you.

  • The commit message follows the same semantics as nixpkgs.

    • You can use a # symbol to specify ambiguities. For example, develop#zsh: <rest of commit message> would tell me that your updating the zsh subprofile living under the develop profile.