<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Compare on CodeInstances.com</title>
    <link>https://codeinstances.com/tags/compare/</link>
    <description>Recent content in Compare on CodeInstances.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://codeinstances.com/tags/compare/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CodeInstances Now Compares Two Runs and Shows Where the Failing One Went Wrong</title>
      <link>https://codeinstances.com/codeinstances-now-compares-two-runs-and-shows-where-the-failing-one-went-wrong/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/codeinstances-now-compares-two-runs-and-shows-where-the-failing-one-went-wrong/</guid>
      <description>&lt;p&gt;CodeInstances v0.2.0 is out, and it adds the third verb. The first release could keep a run and replay it. This one compares two of them: &lt;code&gt;codeinstances diff passing.instance failing.instance&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The usual case goes like this. A job works on Monday and fails on Tuesday, or passes on your laptop and fails in CI. You have both runs as instance files, because you put &lt;code&gt;codeinstances record&lt;/code&gt; in front of the command. Now you want to know what was different, and you&amp;rsquo;d rather not read two logs side by side and guess.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
