kernel-git-commit

Every commit must follow the Conventional Commits specification: https://www.conventionalcommits.org/en/v1.0.0/#specification.

Message format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

1. type — one of feat, fix, refactor, chore, docs, test, build, ci, perf, style, revert. Pick the single type that describes the primary intent of the change.
2. scope — optional, lowercase, the area changed. Use the package, domain, or module name. Use the same scope consistently with recent history.
3. description — imperative mood, lowercase, no trailing period. Summarize what the change does, not how. Max ~72 characters including the type and scope.
4. body — optional. Explain the why and the context, wrapped at 72 characters. Use it when the description alone does not capture the intent.
5. footer — optional. BREAKING CHANGE: <description> for breaking changes, or Refs: #<issue> / Closes: #<issue>.

Rules