All code is not production ready, nor should I be judged on it. Use it at own will to play around.
See doom emacs README
All commit messages should be structured like this:
type(scope): Subject line with at most a 68 character length
Body of the commit message with an empty line between subject and
body. This text should explain what the change does and why it has
been made, *especially* if it introduces a new feature.
Relevant issues should be mentioned if they exist.
Where type
can be one of:
feat
: A new feature has been introducedfix
: An issue of some kind has been fixeddocs
: Documentation or comments have been updatedstyle
: Formatting changes onlyrefactor
: Hopefully self-explanatory!test
: Added missing tests / fixed testschore
: Maintenance work
And scope
should refer to some kind of logical grouping inside of the project.
Please take a look at the existing commit log for examples.