<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ci on Abbreviatory.com</title>
    <link>https://abbreviatory.com/tags/ci/</link>
    <description>Recent content in ci on Abbreviatory.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://abbreviatory.com/tags/ci/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Abbreviatory 0.2 Tells You What Changed Since the Last Test Run</title>
      <link>https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/</guid>
      <description>The first release made one run&amp;rsquo;s output short. This one compares it with the run before. Abbreviatory v0.2.0 keeps a history per command, and every report now opens with what changed: which failures are new, which got fixed, which are still failing and for how long, and which tests are flaky.
Most CI runs aren&amp;rsquo;t news. The same three tests failed yesterday and they fail today. Reading the full report again, or having a coding agent read it again, mostly confirms what everyone already knows.</description>
    </item>
    
  </channel>
</rss>
