<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ci on Companionway</title>
		<link>https://www.companionway.net/categories/ci/</link>
		<description>Recent content in Ci on Companionway</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 17 Aug 2026 11:47:11 -0400</lastBuildDate>
		
			<atom:link href="https://www.companionway.net/categories/ci/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Better CI via commitizen (no pain)</title>
				<link>https://www.companionway.net/post/better_ci_with_commitizen/</link>
				<pubDate>Mon, 17 Aug 2026 11:47:11 -0400</pubDate>
				<guid>https://www.companionway.net/post/better_ci_with_commitizen/</guid>
				<description>&lt;h1 id=&#34;conquering-commitizen-how-i-learned-to-stop-worrying-and-love-the-bump&#34;&gt;Conquering Commitizen: How I Learned to Stop Worrying and Love the Bump&lt;/h1&gt;&#xA;&lt;p&gt;Do you struggle with version control and Continuous Integration (CI)? Have you avoided the pain of using CI tools? Allow me to share my learning experience with Commitizen. The bottom line is once you get past the difference between &lt;code&gt;cz commit&lt;/code&gt; vs &lt;code&gt;git commit&lt;/code&gt; and the benefits of &lt;code&gt;cz bump&lt;/code&gt;, the pain evaporates.&lt;/p&gt;&#xA;&lt;p&gt;For the longest time, version management and keeping changelogs synchronized felt like a tedious tax on software development. You write code, you commit, you fiddle with version strings in source files, you forget to update the changelog, and suddenly your release pipeline is a mess. Then I stumbled into the world of Commitizen, and after a few forehead-scratching moments, the lightbulbs finally went off.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
