ca3937fb82
I think we want to ensure that all new items in headers are documented, and the documentation on modified items is kept up to date. It will take a while to document the backlog of undocumented things, but we can at least ensure that new items don't extend that backlog.
1.1 KiB
1.1 KiB
Motivation
Context
Checklist for maintainers
Maintainers: tick if completed or explain if not relevant
- agreed on idea
- agreed on implementation strategy
- tests, as appropriate
- functional tests -
tests/**.sh - unit tests -
src/*/tests - integration tests -
tests/nixos/*
- functional tests -
- documentation in the manual
- documentation in the internal API docs
- code and comments are self-explanatory
- commit message explains why the change was made
- new feature or incompatible change: updated release notes
Priorities
Add 👍 to pull requests you find important.