Compare commits
4 Commits
feat/herme
...
feat/add-p
| Author | SHA1 | Date | |
|---|---|---|---|
| e9d6262039 | |||
| 49dce32c27 | |||
| dfdc8a309a | |||
| 1cc057bfda |
@@ -25,12 +25,3 @@ This document outlines the development conventions for this NixOS-based infrastr
|
||||
- **Secrets:** Secrets are managed with `agenix`. Edit encrypted files with `agenix -e <file>`.
|
||||
- **Modularity:** Structure configurations into logical, reusable modules under `modules/`. New modules should be registered in `modules/nixos/default.nix` to be available to all hosts.
|
||||
- **Error Handling:** Ensure Nix expressions are robust and handle potential evaluation errors gracefully.
|
||||
|
||||
## Workflow
|
||||
|
||||
- New feature → clean branch from `origin/master` → push → PR on Gitea
|
||||
- Branch naming: `feat/description` (features), `fix/description` (bugs/docs)
|
||||
- Always branch from `origin/master`, never from another feature branch
|
||||
- Submodule changes: commit submodule update in parent repo (the parent commit pins the submodule commit)
|
||||
- PR title should describe the change; body should explain motivation + summary
|
||||
- After PR merge, delete the feature branch
|
||||
|
||||
Submodule assets/compose updated: 1ec22ff3fc...1eacc3cd8e
Reference in New Issue
Block a user