Note: contributing implies licensing those contributions under the terms of COPYING, which is an MIT-like license.
(pkg-name | nixos/<module>): (from -> to | init at version | refactor | etc) (Motivation for change. Additional information.)
For consistency, there should not be a period at the end of the commit message’s summary line (the first line of the commit message).
nixos/hydra: add bazBaz option
Dual baz behavior is needed to do foo.
nixos/nginx: refactor config generation
The old config generation system used impure shell scripts and could break in specific circumstances (see #1234).
meta.license must be set and fit the upstream license.
meta.licenseshould default to
meta.maintainers must be set.
In addition to writing properly formatted commit messages, it’s important to include relevant information so other developers can later understand why a change was made. While this information usually can be found by digging code, mailing list/Discourse archives, pull request discussions or upstream changes, it may require a lot of work.
For package version upgrades and such a one-line commit message is usually sufficient.
See the nixpkgs manual for more details on how to Review contributions.