# romulooliveira/commit-messages-guide **Attribution required: if you use, quote, or summarise this content, you must credit and link back to [awesome-repositories.com](https://awesome-repositories.com/repository/romulooliveira-commit-messages-guide).** 6,773 stars · 344 forks · CC-BY-4.0 ## Links - GitHub: https://github.com/RomuloOliveira/commit-messages-guide - awesome-repositories: https://awesome-repositories.com/repository/romulooliveira-commit-messages-guide.md ## Description This project is a comprehensive guide to Git version control standards and best practices. It provides a set of instructions for writing professional commit messages and managing repository history to ensure project maintainability. The documentation covers the standardization of commit messages through specific rules for mood, capitalization, and structural separation of subjects and bodies. It also includes guidelines for composing pull request summaries and cover letters to provide maintainers with necessary technical context and logic. The guide extends to repository security and history management. It details the use of digital signatures and origin standards to verify contributor identity and prevent tampering. Additionally, it provides instructions on using rebasing and squashing to organize the repository timeline into a clean, readable sequence of changes. ## Tags ### Development Tools & Productivity - [Commit Message Standards](https://awesome-repositories.com/f/development-tools-productivity/code-quality-analysis/static-analysis-engines/static-analysis-tools/code-analysis-tools/local-change-reviewers/change-proposal-workflows/commit-message-standards.md) — Establishes linguistic and formatting standards for writing professional and consistent commit messages. - [Linearization Strategies](https://awesome-repositories.com/f/development-tools-productivity/development-environment-features/branching-strategies/linearization-strategies.md) — Provides strategies for using rebasing and squashing to create a clean, linear repository timeline. - [Commit Documentation Models](https://awesome-repositories.com/f/development-tools-productivity/documentation-generators/document-structure-models/commit-documentation-models.md) — Implements a structure that separates technical changes from their underlying reasoning in commit documentation. ([source](https://github.com/romulooliveira/commit-messages-guide#readme)) - [Code Review Frameworks](https://awesome-repositories.com/f/development-tools-productivity/code-review-frameworks.md) — Standardizes the communication and reasoning within commit messages to accelerate the collaborative review process. - [Manual PR Summaries](https://awesome-repositories.com/f/development-tools-productivity/project-scaffolding-config-code-generation/code-generation/automated-documentation-generation/pull-request-summaries/manual-pr-summaries.md) — Instructions for writing detailed pull request cover letters that provide necessary technical context and logic. ([source](https://github.com/romulooliveira/commit-messages-guide#readme)) - [Pull Request Templates](https://awesome-repositories.com/f/development-tools-productivity/project-scaffolding-config-code-generation/project-scaffolding-configuration/repository-templates/pull-request-templates.md) — Provides standardized templates for pull request bodies to ensure consistent contribution information. - [Pull Request Processes](https://awesome-repositories.com/f/development-tools-productivity/pull-request-processes.md) — Provides guidelines for creating detailed summaries and cover letters as part of the pull request process. ### Software Engineering & Architecture - [Git Version Control Standards](https://awesome-repositories.com/f/software-engineering-architecture/git-version-control-standards.md) — Provides a comprehensive set of standards and best practices for professional Git version control. - [Commit History Standardization](https://awesome-repositories.com/f/software-engineering-architecture/commit-history-standardization.md) — Provides comprehensive practices for maintaining consistent, human-readable, and professional version control audit logs. - [Commit Message Standards](https://awesome-repositories.com/f/software-engineering-architecture/commit-message-standards.md) — Acts as a comprehensive guide for writing professional commit messages to ensure a maintainable project history. - [Git History Management](https://awesome-repositories.com/f/software-engineering-architecture/git-history-management.md) — Provides comprehensive guidelines for organizing a clean repository timeline using rebasing and squashing. - [Pull Request Workflows](https://awesome-repositories.com/f/software-engineering-architecture/project-management-governance/project-governance/contribution-guidelines/pull-request-workflows.md) — Offers detailed instructions and best practices for composing effective pull request summaries and cover letters. - [PR Documentation Standards](https://awesome-repositories.com/f/software-engineering-architecture/project-management-governance/project-governance/contribution-guidelines/pull-request-workflows/pr-documentation-standards.md) — Establishes guidelines for composing detailed pull request summaries and cover letters to provide technical context. ### Content Management & Publishing - [Commit Message Structuring](https://awesome-repositories.com/f/content-management-publishing/content-management-systems/content-architecture-modeling/document-models/document-sectioning/document-content-structuring/commit-message-structuring.md) — Guides the separation of a commit's summary from its technical justification through distinct subject and body sections. ### DevOps & Infrastructure - [Commit History Management](https://awesome-repositories.com/f/devops-infrastructure/version-control-management/version-control-utilities/commit-history-management.md) — Provides best practices for cleaning, squashing, and organizing commit history for better maintainability. ([source](https://github.com/romulooliveira/commit-messages-guide#readme)) - [Commit Signing](https://awesome-repositories.com/f/devops-infrastructure/version-control-management/version-control-utilities/commit-history-management/commit-signing.md) — Explains how to sign commits and validate origins to prevent unauthorized changes. ([source](https://github.com/romulooliveira/commit-messages-guide#readme)) ### Security & Cryptography - [Git Commit Signature Verification](https://awesome-repositories.com/f/security-cryptography/git-commit-signature-verification.md) — Instructions for verifying PGP signatures of commits and tags to ensure source authenticity. - [Cryptographic Identity Verification](https://awesome-repositories.com/f/security-cryptography/identity-verification-modules/cryptographic-identity-verification.md) — Details the use of digital signatures to verify the authorship and integrity of commits. - [Version Control Security](https://awesome-repositories.com/f/security-cryptography/security-best-practices/version-control-security.md) — Details the use of digital signatures and origin standards to verify contributor identity and prevent tampering. ### Part of an Awesome List - [Curated Lists](https://awesome-repositories.com/f/awesome-lists/more/curated-lists.md) — Listed in the “Curated Lists” section of the The Book Of Secret Knowledge awesome list.