conventional-commits

Format git commit messages using the Conventional Commits specification to enable consistent changelogs and automated versioning. This structure enforces a specific header format of type(scope): description to ensure compatibility across CI/CD pipelines.

The conventional commit format indicates a breaking change by adding a `!` after the type or scope, or by including a `BREAKING CHANGE:` footer in the commit body. This ensures automated tooling correctly identifies major version bumps.

Validate conventional commit body and footers by checking against the specification's rules for breaking changes and references. This ensures the type, scope, and body formatting meet the required automated tooling compatibility standards.

Specifying a scope in a conventional commit message is optional. The spec enforces the required type and description, but the scope within the parentheses can be omitted while maintaining automated tooling compatibility.

Yes, you can apply conventional commits formatting when rewriting git history. The specification ensures header format, body, and footer validation remain consistent across various Git workflows.

The Conventional Commits spec enforces specific types like `feat` and `fix` to standardize versioning. These types dictate automated semantic version bumps and improve overall history readability across CI/CD pipelines.