commit-guidelines

Standardize git commit messages by enforcing a gitmoji and type format with issue references. This structure requires an imperative mood and specific type definitions to ensure all team members follow a consistent format for version history traceability.

An effective commit message convention for version control uses a `gitmoji + Type: #issue Subject` structure. It enforces clear rules for commit types, subjects written in imperative mood, and optional body and footer structures to maximize project history traceability.

Format a git commit message by combining a gitmoji, a specific commit type, and an issue reference in the subject line. You must use imperative mood for the subject, and can add optional body and footer structures to provide additional context for code review.

Yes, you can use custom commit types and optional bodies in your git commit guidelines. The convention applies specific type definitions and allows optional body and footer structures to ensure commit message creation and review processes remain clear and consistent within the repository.

Your commit message convention requires imperative mood to maintain clarity and consistency across the repository. Writing subjects in imperative mood standardizes the action description, making the project's version history easier to understand and navigate during code review.

Include a footer in your git commit message when you need to add extra metadata like issue references not covered in the subject. Footers are optional structures in the commit guidelines that provide additional context without cluttering the main subject line.