<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Merge-Queue on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/merge-queue/</link>
    <description>Recent content in Merge-Queue on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/merge-queue/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Merge Queue &amp; PR Gating Bots: Bors-ng vs Kodiak vs Homu Compared 2026</title>
      <link>https://www.pistack.xyz/posts/2026-06-17-self-hosted-merge-queue-pr-gating-bots-bors-ng-kodiak-homu-guide-2026/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-17-self-hosted-merge-queue-pr-gating-bots-bors-ng-kodiak-homu-guide-2026/</guid>
      <description>&lt;h2 id=&#34;why-self-host-a-merge-queue-bot&#34;&gt;Why Self-Host a Merge Queue Bot?&lt;/h2&gt;&#xA;&lt;p&gt;Modern development teams use merge queues to protect their main branch from broken builds. Instead of merging PRs immediately after approval, a merge queue bot serializes merges, tests each one against the latest main, and only merges if all checks pass. This eliminates &amp;ldquo;merge skew&amp;rdquo; — the scenario where two PRs pass CI independently but break when merged together.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
