| Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ie3244add8420632017132c20c804fd6ecab3a4e0
Reviewed-on: https://cl.fcuny.net/c/world/+/164
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
|
Change-Id: I94e28dc52d69c3c2ee4d59a0109c9ae32402fb2c
|
|
In order to write good commit message, having a reminder of how to write
them is useful. This template provides some guidance to categorize the
change and how to phrase the description.
|
|
|
|
All the modules that are needed for home-manager should be under
`home/`, and each host will have a `host.nix` where the modules are
enabled as needed. Later on we can create some profiles to make it
easier to consume the configuration.
I apply this only to tahoe for now, as the amount of packages needed for
my user are pretty limited.
|
|
Move the configuration for git that requires the signing to pass, and
use the `pass-git-helper` to manage the secrets.
|
|
|
|
|
|
And use the default key for signing with git.
|
|
I need something to help with lint/validation ...
|
|
|
|
|
|
|
|
Add git configuration and move go to its own module.
|