<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Apex Actions blog</title>
    <link>https://apexactions.com/blog/</link>
    <description>Engineering notes from Apex Actions: how the product decides what it decides.</description>
    <language>en</language>
    <atom:link href="https://apexactions.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Thu, 20 Aug 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>A flaky test is a disagreement at one commit, not a failure rate</title>
      <link>https://apexactions.com/blog/flaky-test-is-a-disagreement/</link>
      <guid isPermaLink="true">https://apexactions.com/blog/flaky-test-is-a-disagreement/</guid>
      <description>Why we count commits that disagreed, and why the pull request only ever sees one warning.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Apex Actions engineering</dc:creator>
      <category>engineering</category>
      <category>flaky-tests</category>
    </item>
    <item>
      <title>&quot;Why did nothing run?&quot; now has an answer</title>
      <link>https://apexactions.com/blog/why-did-nothing-run/</link>
      <guid isPermaLink="true">https://apexactions.com/blog/why-did-nothing-run/</guid>
      <description>Every push now leaves a verdict for every workflow file, including the ones that ran nothing — and names the filter that said no.</description>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Apex Actions engineering</dc:creator>
      <category>engineering</category>
      <category>product</category>
    </item>
  </channel>
</rss>
