sf-commit-convention

Enforcing conventional commit messages across git workflows requires automated validation rules that check commit format, detect legacy refs, validate issue references, and append mandatory trailers like Assisted-by to ensure compliant, traceable changes.

Branch naming patterns for conventional commits use a prefix/issue-description format, requiring an issue number and description length validation. Allowed prefixes include feat, fix, docs, chore, refactor, ci, test, and release to categorize changes consistently.

Adding an Assisted-by trailer to git commit messages requires a convention enforcement tool that automatically detects format, validates issue references, and appends the mandatory trailer during commit creation to ensure compliant changes.

Commit convention enforcement supports legacy git reference formats by detecting legacy refs and guiding users toward correct conventional commit styles. It validates fully-qualified issue paths to ensure cross-repo traceability while transitioning teams to updated conventions.

Validating pull request titles against conventional commit rules is supported across typical development workflows. The enforcement checks title format, issue references, and mandatory trailers to ensure merge request titles match the same standards as commit messages.

Automated branch naming and commit validation is limited to specific allowed prefixes like feat, fix, docs, chore, refactor, ci, test, and release. It requires issue numbers in branch names and enforces description length, which may restrict teams using non-standard naming conventions.