---
title: "💭 Conventional Commits"
description: "!https://www.conventionalcommits.org/en/v1.0.0/"
date: 2025-06-17
published: true
tags:
  - dev
  - thought
template: link
---


<div class="embed-card embed-card-external">
  <a href="https://www.conventionalcommits.org/en/v1.0.0/" class="embed-card-link" target="_blank" rel="noopener noreferrer">
    <div class="embed-card-content">
      <div class="embed-card-title">Conventional Commits</div>
      <div class="embed-card-description">A specification for adding human and machine readable meaning to commit messages</div>
      <div class="embed-card-meta">Conventional Commits &middot; conventionalcommits.org</div>
    </div>
  </a>
</div>


I try to use conventional commits on all of my commits, but I often end up only using feat/fix.  I need to keep this page handy and get new verbiage worked into my language 

* fix:
* feat:
* build:
* chore:
* ci:
* docs:
* style:
* refactor:
* perf:
* test:

Optionally include a scope `fix(parser):`

A bang indicates a breaking change note. For example ...

``` bash
chore!: drop support for Node 6

BREAKING CHANGE: use JavaScript features not available in Node 6.
```

!!! note

    This post is a <a href="/thoughts/" class="wikilink" data-title="Thoughts" data-description="These are generally my thoughts on a web page or some sort of url, except a rare few don&#39;t have a link. These are dual published off of my..." data-date="2024-04-01">thought</a>. It's a short note that I make
    about someone else's content online <a href="/tags/thoughts/" class="hashtag-tag" data-tag="thoughts" data-count=2 data-reading-time=3 data-reading-time-text="3 minutes">#thoughts</a>