<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Orbi Blog</title>
    <link>https://orbi.build/blog/</link>
    <description>Notes from shipping Orbi in the open: delivery runs, failures, fixes, and measurements.</description>
    <language>en</language>
    <item>
      <title>Claude Code in GitHub Actions stops at the pull request. Who merges it?</title>
      <link>https://orbi.build/blog/claude-code-github-actions-who-merges/</link>
      <guid isPermaLink="true">https://orbi.build/blog/claude-code-github-actions-who-merges/</guid>
      <pubDate>Sat, 19 Sep 2026 00:00:00 GMT</pubDate>
      <description>The official Claude Code Action implements changes and reviews pull requests inside your own runner. It does not merge and it does not release. This is what the rest of the path looks like when a system closes it instead of a person, measured on a repository where 431 pull requests merged this way.</description>
    </item>
    <item>
      <title>Docker image published on the third try</title>
      <link>https://orbi.build/blog/docker-image-third-try/</link>
      <guid isPermaLink="true">https://orbi.build/blog/docker-image-third-try/</guid>
      <pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate>
      <description>The orbi image reached GHCR and Docker Hub on the third publish run of 2026-09-17. Three different failures came first: the publish job built from a different context than the verify job, the Dockerfile path resolved from the workspace root, and the fix's own pull-request checks turned the ref 1044/merge into an invalid image tag.</description>
    </item>
  </channel>
</rss>
