<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Commit-Conventions on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/commit-conventions/</link>
    <description>Recent content in Commit-Conventions on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/commit-conventions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Git Commit Convention Tools: Commitizen vs Commitlint vs Cocogitto Compared</title>
      <link>https://www.pistack.xyz/posts/2026-06-17-self-hosted-git-commit-convention-tools-commitizen-commitlint-cocogitto/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-17-self-hosted-git-commit-convention-tools-commitizen-commitlint-cocogitto/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Consistent commit messages are the backbone of maintainable software projects. Whether you&amp;rsquo;re generating changelogs automatically, calculating semantic version bumps, or simply helping your team understand the history of changes, following a commit convention like &lt;a href=&#34;https://www.conventionalcommits.org/&#34;&gt;Conventional Commits&lt;/a&gt; makes a measurable difference.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
