<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Code-Review on ROBOCO</title>
    <link>https://roboco.io/en/tags/code-review/</link>
    <description>Recent content in Code-Review on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Oct 2026 10:00:00 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/code-review/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Software Factory Best Practices from Open-Source Projects (2/4): Who Merges?</title>
      <link>https://roboco.io/en/posts/software-factory-who-merges/</link>
      <pubDate>Sat, 10 Oct 2026 10:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/software-factory-who-merges/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;(Changes to migration, schema, and sync paths get) a real human review before merge — no exceptions, no self-merge, no bot-only approval.&amp;rdquo; – Beads &lt;code&gt;PR_MAINTAINER_GUIDELINES.md&lt;/code&gt;&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;This is the second post in the four-part series &amp;ldquo;Software Factory Best Practices from Open-Source Projects.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;The series&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://roboco.io/en/posts/software-factory-best-practices-from-open-source/&#34;&gt;The Criteria and 12 Repositories: what counts as a factory, and where factories are running&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Who Merges? Risk-based delegation and permission structures (this post)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://roboco.io/en/posts/software-factory-evidence-before-fix/&#34;&gt;Factories That Filter by Evidence: proving a test &amp;ldquo;fails before the fix&amp;rdquo;&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://roboco.io/en/posts/software-factory-failures-into-rules/&#34;&gt;Turning Failures into Rules: self-improvement loops and their limits&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;In &lt;a href=&#34;https://roboco.io/en/posts/software-factory-best-practices-from-open-source/&#34;&gt;Part 1&lt;/a&gt;, I reverse-engineered 12 public repositories and classified eight of them as software factories.&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; Of those, OpenClaw was the only one where I confirmed bots merging into the main branch at scale. In the other factories, final merges were mostly made by people, and those merges were usually concentrated in one person.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Software Factory Best Practices from Open-Source Projects (3/4): Factories That Filter by Evidence</title>
      <link>https://roboco.io/en/posts/software-factory-evidence-before-fix/</link>
      <pubDate>Sat, 10 Oct 2026 10:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/software-factory-evidence-before-fix/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;Your test is NOT VALID if it passes with &lt;code&gt;USE_SYSTEM_BUN=1&lt;/code&gt;.&amp;rdquo; – Bun &lt;code&gt;CLAUDE.md&lt;/code&gt;&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;This is the third post in the four-part series &amp;ldquo;Software Factory Best Practices from Open-Source Projects.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;The series&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://roboco.io/en/posts/software-factory-best-practices-from-open-source/&#34;&gt;The Criteria and 12 Repositories: what counts as a factory, and where factories are running&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://roboco.io/en/posts/software-factory-who-merges/&#34;&gt;Who Merges? Risk-based delegation and permission structures&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Factories That Filter by Evidence: proving a test &amp;ldquo;fails before the fix&amp;rdquo; (this post)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://roboco.io/en/posts/software-factory-failures-into-rules/&#34;&gt;Turning Failures into Rules: self-improvement loops and their limits&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;The quote at the top comes from the agent instructions in the Bun repository. &lt;code&gt;USE_SYSTEM_BUN=1&lt;/code&gt; is a setting that runs the tests against the existing Bun release, before the fix. In other words, the rule says that &amp;ldquo;a test that also passes on the unfixed code proves nothing.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
