### Commit with No Body Source: https://www.conventionalcommits.org/en/v1.0.0 A simple commit message example for documentation changes, consisting only of the type and description, with no additional body or footers. ```git docs: correct spelling of CHANGELOG ``` -------------------------------- ### Conventional Commit Revert Example Source: https://www.conventionalcommits.org/en/v1.0.0 Use the `revert` type with a footer referencing the commit SHAs being reverted. This is a recommended approach for handling revert commits. ```git revert: let us never again speak of the noodle incident Refs: 676104e, a215868 ``` -------------------------------- ### Commit with Description and Breaking Change Footer Source: https://www.conventionalcommits.org/en/v1.0.0 Example of a 'feat' type commit that introduces a new feature and includes a 'BREAKING CHANGE' footer to indicate an API modification. ```git feat: allow provided config object to extend other configs BREAKING CHANGE: `extends` key in config file is now used for extending other config files ``` -------------------------------- ### Commit with Scope Source: https://www.conventionalcommits.org/en/v1.0.0 Example of a commit message that includes a scope to specify the area of the codebase affected by the change, in this case, language features. ```git feat(lang): add Polish language ``` -------------------------------- ### Commit with Scope and '!' for Breaking Change Source: https://www.conventionalcommits.org/en/v1.0.0 Shows how to combine a scope with the '!' notation to indicate a breaking change within a specific part of the codebase. ```git feat(api)!: send an email to the customer when a product is shipped ``` -------------------------------- ### Commit with Multi-paragraph Body and Multiple Footers Source: https://www.conventionalcommits.org/en/v1.0.0 A detailed commit message demonstrating a multi-paragraph body for explaining a fix and including multiple footers for review and references. ```git fix: prevent racing of requests Introduce a request id and a reference to latest request. Dismiss incoming responses other than from latest request. Remove timeouts which were used to mitigate the racing issue but are obsolete now. Reviewed-by: Z Refs: #123 ``` -------------------------------- ### Commit with '!' and BREAKING CHANGE Footer Source: https://www.conventionalcommits.org/en/v1.0.0 Illustrates a commit that uses both the '!' notation and a 'BREAKING CHANGE' footer to clearly communicate a significant API alteration. ```git feat!: drop support for Node 6 BREAKING CHANGE: use JavaScript features not available in Node 6. ``` -------------------------------- ### Conventional Commit Structure Source: https://www.conventionalcommits.org/en/v1.0.0 Defines the basic structure of a conventional commit message, including type, optional scope, description, optional body, and optional footers. ```text [optional scope]: [optional body] [optional footer(s)] ``` -------------------------------- ### Commit with '!' for Breaking Change Source: https://www.conventionalcommits.org/en/v1.0.0 Demonstrates using an exclamation mark '!' after the commit type to signify a breaking change, drawing attention to the API modification. ```git feat!: send an email to the customer when a product is shipped ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.