
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Ryan Todd</title>
      <link>https://ryantodd.dev/blog</link>
      <description>Notes on AI, operational automation, cloud infrastructure, and platform engineering.</description>
      <language>en-us</language>
      <managingEditor>rmtodd618@gmail.com (Ryan Todd)</managingEditor>
      <webMaster>rmtodd618@gmail.com (Ryan Todd)</webMaster>
      <lastBuildDate>Sat, 18 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://ryantodd.dev/tags/github-actions/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://ryantodd.dev/blog/the-pr-check-that-reads-your-readme</guid>
    <title>The PR Check That Reads Your README</title>
    <link>https://ryantodd.dev/blog/the-pr-check-that-reads-your-readme</link>
    <description>Documentation rots because keeping it current is nobody&#39;s job at merge time. I added an advisory PR check that asks a model one question: does this change make the README wrong? Its first two verdicts taught me something I didn&#39;t expect about what a check like this can and can&#39;t do.</description>
    <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
    <author>rmtodd618@gmail.com (Ryan Todd)</author>
    <category>ci-cd</category><category>github-actions</category><category>ai</category><category>documentation</category><category>platform-engineering</category>
  </item>

    </channel>
  </rss>
