<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Erol Ege ERKAN on Medium]]></title>
        <description><![CDATA[Stories by Erol Ege ERKAN on Medium]]></description>
        <link>https://medium.com/@erolegeerkan?source=rss-b182d2f35693------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4SReKdth1L19IOiRiM7EwQ.png</url>
            <title>Stories by Erol Ege ERKAN on Medium</title>
            <link>https://medium.com/@erolegeerkan?source=rss-b182d2f35693------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:03:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erolegeerkan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What about Clean Commits?]]></title>
            <link>https://medium.com/@erolegeerkan/what-about-clean-commits-e58cf036fc7b?source=rss-b182d2f35693------2</link>
            <guid isPermaLink="false">https://medium.com/p/e58cf036fc7b</guid>
            <category><![CDATA[clean-architecture]]></category>
            <category><![CDATA[conventional-commits]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[clean-code]]></category>
            <dc:creator><![CDATA[Erol Ege ERKAN]]></dc:creator>
            <pubDate>Fri, 11 Jul 2025 11:20:14 GMT</pubDate>
            <atom:updated>2025-07-11T11:20:14.553Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>We often talk about Clean Architecture and Clean Code in software development but what about Clean Commits?</strong></blockquote><p>In software development, Clean Architecture and Clean Code concepts are essential to a better developer experience. With them, we put our code and structure into a template that anyone who knows that template can understand. They are like a common tongue in software development.</p><h3>What about Clean Commits?</h3><p>Yes, writing clean code and making our projects better with clean architecture are best practices and they should be. But we forgot something to complete the Clean Trilogy, which is Clean Commits.</p><blockquote><strong>Have you ever opened your project’s commit history to find that special commit?</strong></blockquote><p>We all do that when we want to understand what happened or which changes were made by our teammates. But at that time, it is hard to find which commit specifically involves the part we are looking for. This is because our commit history consists of different commit messages such as “Fix UI,” “Login Screen -&gt; TextField changes,” or just an issue tag related to the commit itself, like “12345.”</p><blockquote><strong>Can we improve all these commits by using naming conventions, just like one of the essentials when writing clean code?</strong></blockquote><p>Of course, we can. We are developers, we have superpowers!</p><p>So, at this point in my article, it is time to talk about Conventional Commits, which I like to call Clean Commits to complete the Clean Trilogy.😊</p><p><a href="https://www.conventionalcommits.org/en/v1.0.0/">Conventional Commits</a></p><p>Conventional Commits are “a specification for adding human and machine readable meaning to commit messages,” as mentioned on their official website. They provide a set of rules for better and more understandable commit messages, with structured commit messages as follows:</p><pre>&lt;type&gt;[optional scope]: &lt;description&gt; [optional body] [optional footer(s)]</pre><ul><li>The “type” section stands for the type of commit. It can be a feature with the “feat” type for adding new features, or it can be a “fix” for representing bug fixes in the code, and so on.</li><li>The “optional scope” part is optional. For example, if a newly added feature is related to your API, you can commit it like this:</li></ul><pre>feat(api): ...</pre><ul><li>The “description” part is important for readable and understandable commit messages. It should be as descriptive as possible. I use the present tense for all of my commits, but you can simply create your own rule.</li><li>After those parts, we have the “optional body” and “optional footer” sections. These are optional, but they are useful for adding your issue tag with your commit, which helps link issues related to that commit for better investigation in the future when necessary.</li></ul><h3><strong>Create Your Own Commit Template</strong></h3><p>I think a better approach is to create your own commit template tailored to your project and its needs.</p><p>For example, you can create your own type names. Maybe your team is using an external package called “hello,” so you can create a type “hello” to use whenever you make changes related to that package. These examples can go a long way. It’s totally up to you and your team.</p><p>For instance, maybe you want to highlight your commit type and issue tag related to that commit, like I do. I use the commit types below to highlight these parts with different types of brackets.</p><pre>{feat} : Add new login implementations [#20]</pre><p>With this commit template, when I look at the commit history of my projects, I can easily understand and investigate further whenever needed.</p><p>So, it is totally up to you and your team to create your own template for your needs. There are no restrictions.</p><h3>Better CI/CD with Clean Commits?</h3><blockquote><strong>Yes, of course. First of all, we create a template to speak a common tongue in commits, which already affects our CI/CD pipeline a lot. But what about more?</strong></blockquote><p>You can create jobs in your pipeline based on your commit messages. For example, if your commit message contains the keyword “test” as the type, then run the related tests; if your commit message contains “docs,” then update the documentation accordingly. There are many good opportunities to control your automated jobs with your commits.</p><p>And there’s more. In Azure DevOps, you can tag your issue like I showed below using “#”, and the system automatically adds your related tasks to your pull request.</p><pre>{test} : Add tests for login process [#23]</pre><ul><li>For example, in this case, our task with the ID of 23 is added to our pull request automatically by Azure DevOps itself.</li></ul><p>You can checkout <a href="https://stackoverflow.com/questions/54577475/azuredevops-link-git-commit-or-branch-to-work-item-via-command-line/54577835">this writing</a> on StackOverFlow for further research.</p><p>And there are good CLI tools for checking whether your commit follows your commit structure or not, you can use these too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItJr_Z281g1IRVtDe9FkXQ.png" /><figcaption>Commit templates improve readability and understandability.</figcaption></figure><p>Now it’s your time to complete your project’s Clean Trilogy with Clean Commits 😎.</p><p>Thank you for reading! Have a great day with an even better developer experience!</p><p>See you later in another article! 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e58cf036fc7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>