<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Workflow on Omar Crosby</title>
    <link>https://omarcrosby.com/tags/workflow/</link>
    <description>Recent content in Workflow on Omar Crosby</description>
    <image>
      <title>Omar Crosby</title>
      <url>https://omarcrosby.com/images/og.jpg</url>
      <link>https://omarcrosby.com/images/og.jpg</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 20 Jul 2026 09:12:12 -0400</lastBuildDate>
    <atom:link href="https://omarcrosby.com/tags/workflow/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Conventional Commits, and the thinking they encourage</title>
      <link>https://omarcrosby.com/posts/conventional-commits-and-the-thinking-they-encourage/</link>
      <pubDate>Mon, 20 Jul 2026 09:12:12 -0400</pubDate>
      <guid>https://omarcrosby.com/posts/conventional-commits-and-the-thinking-they-encourage/</guid>
      <description>A working tour of Conventional Commits — the format, the reason it makes each changeset better before any tool touches it, how to identify good scopes, what the Angular convention adds on top, and where the whole thing fits into the release-automation ecosystem (semantic-release, release-please, cocogitto, git-cliff, commitlint).</description>
    </item>
  </channel>
</rss>
