<h2 id="heading-so-what-is-a-conventional-commit">So, what is a Conventional Commit?</h2>
<p>Conventional Commits is a lightweight convention on top of commit messages. In simple, pre-fix the commit messages with some sets of pre-defined rules. It makes commit self-explanatory what type of commit it is.</p>
<h3 id="heading-syntax">Syntax :</h3>
<p>The commit message should follow a structure like this:</p>
<p><code>&lt;type&gt;[optional scope]: &lt;description&gt;</code></p>
<p><strong>For Eg: If we are improving documentation in the README</strong></p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1657076433603/HWkgzToj6.png" alt="Commit message (2).png" /></p>
<h2 id="heading-use-of-conventional-commits">Use of Conventional Commits</h2>
<ul>
<li>Automatically generating CHANGELOG files.</li>
<li>Create auto releases with semantic versioning. </li>
<li>Auto trigger builds.</li>
<li>Get a more structured and understandable commit history.</li>
</ul>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1657080466833/vCo7pc2Qj.png" alt="Untitled design.png" /></p>
<p>Commit history of <a target="_blank" href="https://github.com/Pradumnasaraf/open-source-with-pradumna">EddieHub's LinkFree project</a></p>
<h2 id="heading-some-commonly-used-conventions">Some commonly-used conventions.</h2>
<ul>
<li><code>chore:</code> Changes that don't change source code or tests.</li>
<li><code>docs:</code> Changes to the documentation.</li>
<li><code>feat:</code> Added new feature.</li>
<li><code>ci:</code> Changes to CI configuration files.</li>
<li><code>fix:</code> A bug fix</li>
<li><code>build:</code> Changes that affect the build system or external dependencies.</li>
<li><code>style:</code> Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)</li>
<li><code>test:</code> Adding missing tests or correcting existing tests</li>
</ul>
<p>To learn more about it, visit <a target="_blank" href="https://www.conventionalcommits.org/en/v1.0.0/">https://www.conventionalcommits.org</a></p>


## So, what is a Conventional Commit?

Conventional Commits is a lightweight convention on top of commit messages. In simple, pre-fix the commit messages with some sets of pre-defined rules. It makes commit self-explanatory what type of commit it is.

### Syntax :

The commit message should follow a structure like this:

`<type>[optional scope]: <description>`

**For Eg: If we are improving documentation in the README**

![Commit message (2).png](https://cdn.hashnode.com/res/hashnode/image/upload/v1657076433603/HWkgzToj6.png align="left")

## Use of Conventional Commits

- Automatically generating CHANGELOG files.
- Create auto releases with semantic versioning. 
- Auto trigger builds.
- Get a more structured and understandable commit history.

![Untitled design.png](https://cdn.hashnode.com/res/hashnode/image/upload/v1657080466833/vCo7pc2Qj.png align="left")

Commit history of [EddieHub's LinkFree project](https://github.com/Pradumnasaraf/open-source-with-pradumna)

## Some commonly-used conventions.

- `chore:` Changes that don't change source code or tests.
- `docs:` Changes to the documentation.
- `feat:` Added new feature.
- `ci:` Changes to CI configuration files.
- `fix:` A bug fix
- `build:` Changes that affect the build system or external dependencies.
- `style:` Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
- `test:` Adding missing tests or correcting existing tests

To learn more about it, visit [https://www.conventionalcommits.org](https://www.conventionalcommits.org/en/v1.0.0/)

Learn how to optimize commit messages with Conventional Commits - a lightweight convention for better structured commit history

Conventional Commits: Start now

Getting started with Conventional Commits

So, what is a Conventional Commit?

Syntax :

Use of Conventional Commits

Some commonly-used conventions.

Pradumna is a Developer Advocate, Docker Captain, and a DevOps and Go Developer. He is passionate about Open Source and has mentored hundreds of people to break into the ecosystem.


Hey, I like to talk about Open Source and DevOps. Do follow and subscribe to the blog to get notified whenever I post something new.

Getting started with Conventional Commits

Table of contents

So, what is a Conventional Commit?

Syntax :

Use of Conventional Commits

Some commonly-used conventions.