swpm-conventional-commits

Git commit message formatting for SWPM uses Conventional Commits 1.0.0 standards. You must include a mandatory type, an optional scope, and proper body and footer sections to ensure consistent history and clear release notes.

Automated changelog generation requires a conventional commits structure with a mandatory type like feat or fix, an optional scope, and body or footer sections for breaking changes and references to standardize release planning.

To indicate breaking changes in a conventional commit message, use specific body and footer conventions. The standard requires these sections to document breaking changes and references for SWPM workflows and release processes.

You can use conventional commits with custom scopes in CI pipelines. The standard applies when writing or modifying commits across SWPM workflows and CI pipelines, supporting mandatory types with optional scopes for validation.

A commit type and scope are needed for SWPM release processes to enforce consistent message structure. This standardization improves release planning and changelog generation by identifying features, fixes, and breaking changes across projects.