--- title: Why Conventional Commits are worth the discipline description: A developer shares their experience adopting Conventional Commits and Conventional Branches after attending a conference talk, then scaling the practice across... canonical: https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why Conventional Commits are worth the discipline | daily.dev og:description: A developer shares their experience adopting Conventional Commits and Conventional Branches after attending a conference talk, then scaling the practice across... og:url: https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat og:image: https://api.daily.dev/og/posts/r8rRq9Rat.png og:image:alt: Why Conventional Commits are worth the discipline og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why Conventional Commits are worth the discipline **[All Things Open](https://daily.dev/sources/allthingsopen)** · 5 min read · 14 upvotes · 1 comments ## Summary A developer shares their experience adopting Conventional Commits and Conventional Branches after attending a conference talk, then scaling the practice across a real Power BI dashboard migration to GitHub. The post explains how the conventions were adapted for non-GitHub request sources (e.g., ServiceNow tickets, ad hoc requests), how commit history made stakeholder communication easier, and how GitHub's release feature benefits from structured branch names. The author encourages skeptics to start small with a side project to build the muscle memory. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What did Conventional Branches version 1.1.0 add for AI-generated code? Conventional Branches v1.1.0 added source prefixes for AI agents that generate code. This enables tool validation and a registration standard, and lets human reviewers identify which pull requests were generated by AI agents rather than human developers, making review and accountability easier in mixed human-AI workflows. _Developers tracking AI-generated pull requests can follow branch naming standards like this via daily.dev._ ### How do you name a Conventional Branch for a request that comes from a ServiceNow ticket instead of a GitHub issue? Name the branch using a prefix like feat/snow-inc8675309, referencing the ServiceNow incident number, instead of the standard feat/issue-123 pattern meant for GitHub issues. Ad hoc requests without a formal ticket can instead use a pattern such as feat/ad-hoc-feature-here, or a GitHub issue can be created first for consistency. _Teams juggling multiple request sources can compare branching conventions like this on daily.dev before standardizing their own._ ## Community discussion Top comments from developers on daily.dev. **@agustinbarrientos** · 0 upvotes > The AI source prefix should come first ## Similar posts on daily.dev - [Branching Paths](https://daily.dev/posts/branching-paths-fw2ymkinb) · The Daily WTF · 0 upvotes · 0 comments - [Build Wide, Ship Narrow](https://daily.dev/posts/build-wide-ship-narrow-ubltyfimm) · Hacker News · 0 upvotes · 0 comments --- Tags: [#cicd](https://daily.dev/tags/cicd), [#git](https://daily.dev/tags/git), [#version-control](https://daily.dev/tags/version-control), [#power-bi](https://daily.dev/tags/power-bi) [View this post on daily.dev](https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why Conventional Commits are worth the discipline","url":"https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat"},"datePublished":"2026-08-04T06:23:33.239Z","dateModified":"2026-09-13T20:44:02.285Z","description":"A developer shares their experience adopting Conventional Commits and Conventional Branches after attending a conference talk, then scaling the practice across...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7fdd5d477a5ae0163751f87d20061a57?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7fdd5d477a5ae0163751f87d20061a57?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"All Things Open","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"All Things Open","logo":"https://media.daily.dev/image/upload/s--dgFP6zAp--/f_auto/v1720885901/logos/allthingsopen","url":"https://daily.dev/sources/allthingsopen"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":14},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"cicd,git,version-control,power-bi","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"All Things Open","item":"https://daily.dev/sources/allthingsopen"},{"@type":"ListItem","position":3,"name":"Why Conventional Commits are worth the discipline"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat","comment":[{"@type":"Comment","text":"The AI source prefix should come first","datePublished":"2026-08-15T22:12:42.214Z","url":"https://daily.dev/posts/r8rRq9Rat#c-OWw97dglb","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-conventional-commits-are-worth-the-discipline-r8rrq9rat#faq","mainEntity":[{"@type":"Question","name":"What did Conventional Branches version 1.1.0 add for AI-generated code?","acceptedAnswer":{"@type":"Answer","text":"Conventional Branches v1.1.0 added source prefixes for AI agents that generate code. This enables tool validation and a registration standard, and lets human reviewers identify which pull requests were generated by AI agents rather than human developers, making review and accountability easier in mixed human-AI workflows. Developers tracking AI-generated pull requests can follow branch naming standards like this via daily.dev."}},{"@type":"Question","name":"How do you name a Conventional Branch for a request that comes from a ServiceNow ticket instead of a GitHub issue?","acceptedAnswer":{"@type":"Answer","text":"Name the branch using a prefix like feat/snow-inc8675309, referencing the ServiceNow incident number, instead of the standard feat/issue-123 pattern meant for GitHub issues. Ad hoc requests without a formal ticket can instead use a pattern such as feat/ad-hoc-feature-here, or a GitHub issue can be created first for consistency. Teams juggling multiple request sources can compare branching conventions like this on daily.dev before standardizing their own."}}]} ```