# conventional-commits/conventionalcommits.org

**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/conventional-commits-conventionalcommits-org).**

8,581 stars · 654 forks · SCSS · mit

## Links

- GitHub: https://github.com/conventional-commits/conventionalcommits.org
- Homepage: https://conventionalcommits.org
- awesome-repositories: https://awesome-repositories.com/repository/conventional-commits-conventionalcommits-org.md

## Topics

`commit` `convention` `conventional-changelog` `conventional-commits` `git` `specification` `standard`

## Description

This project provides a specification for a structured commit message convention that enables automated semantic versioning and changelog generation. It defines a standard grammar for commit messages to ensure project history is readable by both humans and machines.

The specification maps specific commit types and breaking change indicators to version increment logic, allowing tools to automatically determine whether a patch, minor, or major release is required. This standardized format also facilitates the automatic production of human-readable release notes by parsing commit history.

The convention serves as a foundation for automation, providing a predictable metadata format that external tools use to trigger build, test, and deployment workflows within continuous integration pipelines.

## Tags

### DevOps & Infrastructure

- [Commit-Based Versioning Engines](https://awesome-repositories.com/f/devops-infrastructure/version-control-automation/commit-based-versioning-engines.md) — Implements the core logic for determining semantic version increments by analyzing commit message types.
- [CI CD Pipelines](https://awesome-repositories.com/f/devops-infrastructure/ci-cd-pipelines.md) — Facilitates the automatic initiation of build, test, and deployment workflows through standardized commit types.
- [CI/CD Workflows](https://awesome-repositories.com/f/devops-infrastructure/ci-cd-workflows.md) — Provides a standardized message format used to signal and trigger specific build and deployment pipelines.
- [Release Automation](https://awesome-repositories.com/f/devops-infrastructure/release-automation.md) — Enables automated deployment pipelines to execute based on the nature and impact of changes identified in commits. ([source](https://www.conventionalcommits.org/fr/))

### Content Management & Publishing

- [Breaking Change Indicators](https://awesome-repositories.com/f/content-management-publishing/content-management-systems/versioning-change-tracking/breaking-change-indicators.md) — Uses specific tokens and modifiers to signal incompatible API changes, triggering major version increments. ([source](https://www.conventionalcommits.org/id/))

### Data & Databases

- [Commit Message Parsers](https://awesome-repositories.com/f/data-databases/atomic-commit-logs/catalog-based-commit-coordinators/commit-message-parsers.md) — Establishes a grammar that allows tools to parse commit types and scopes using regular expressions.

### Development Tools & Productivity

- [Commit History Analysis](https://awesome-repositories.com/f/development-tools-productivity/commit-history-analysis.md) — Provides a specification for programmatically scanning and analyzing git commit logs to determine release scope.
- [Commit Standards](https://awesome-repositories.com/f/development-tools-productivity/commit-standards.md) — Defines a rigid, standardized grammar for commit messages to ensure interoperability between automation tools.
- [Release Changelog Generators](https://awesome-repositories.com/f/development-tools-productivity/project-changelogs/release-changelog-generators.md) — Defines a standard for transforming parsed commit metadata into structured, human-readable release notes.
- [Build Automation](https://awesome-repositories.com/f/development-tools-productivity/workflow-automation-tools/build-task-automation/build-automation.md) — Provides a predictable metadata format that allows external tools to automatically trigger build and publishing workflows. ([source](https://www.conventionalcommits.org/))

### Software Engineering & Architecture

- [Breaking Change Detectors](https://awesome-repositories.com/f/software-engineering-architecture/architectural-design-patterns/state-management/change-detection/breaking-change-detectors.md) — Specifies tokens and footer keywords used to signal breaking changes for automated versioning.
- [Change Intent Communication](https://awesome-repositories.com/f/software-engineering-architecture/change-intent-communication.md) — Uses a consistent, structured format to signal the nature of changes to human stakeholders. ([source](https://www.conventionalcommits.org/en/v1.0.0-beta.3))
- [CI/CD Integrations](https://awesome-repositories.com/f/software-engineering-architecture/integration-extensibility/workflow-automation-integrations/ci-cd-integrations.md) — Acts as a standardized integration point between developer commit history and CI/CD automation tools. ([source](https://www.conventionalcommits.org/pr/))