conventional-commit

To write a conventional commit message, structure it with an imperative concise header, an optional scope and body, and footer conventions for breaking changes or issue references. This machine-readable format allows tooling to automate changelog generation and semantic version bumps.

The conventional commit format uses footer conventions to indicate breaking changes, often marked with a specific notation. It requires an imperative concise header and optional scope and body to ensure the commit message is machine-readable for semantic version bumping.

Structure your git commit message for semantic versioning by applying the Conventional Commits specification. Use an imperative concise header, an optional scope and body, and footers for issue references or breaking changes to trigger automated release generation.

Yes, you can use conventional commits to draft messages before coding. This guided authoring approach helps define an imperative concise header, scoped changes, and descriptive bodies upfront, ensuring consistent software development workflows.

A conventional commit message does not require a body and scope; they are optional. The specification mandates an imperative concise header, while the optional body and footer conventions are used for descriptive details, breaking changes, and issue references.

You should use conventional commits instead of plain git messages to solve the problem of inconsistent and ambiguous history. This structure provides a clear, repeatable format that both machines and humans can parse reliably for automating changelogs and releases.