<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI-CD on Go Micro</title><link>https://go-micro.dev/tags/ci-cd.html</link><description>Recent content in CI-CD on Go Micro</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 29 Jul 2026 08:42:34 +0100</lastBuildDate><atom:link href="https://go-micro.dev/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>The Loop, Shipped: Introducing micro loop</title><link>https://go-micro.dev/blog/2026/07/02/the-loop-shipped-introducing-micro-loop.html</link><pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate><guid>https://go-micro.dev/blog/2026/07/02/the-loop-shipped-introducing-micro-loop.html</guid><description>&lt;p&gt;A few weeks ago we wrote &lt;a href="https://go-micro.dev/blog/2026/06/25/how-go-micro-builds-itself/"&gt;How Go Micro Builds Itself&lt;/a&gt;: a loop of two AI agents — Codex writing scoped increments, Claude Code orchestrating and reviewing, a human setting direction — kept honest by CI. It was our own thesis, &lt;em&gt;an agent operating a system&lt;/em&gt;, pointed at the repository that defines the thesis.&lt;/p&gt;
&lt;p&gt;People asked the obvious question: &lt;strong&gt;can I run that on my repo?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Now you can. &lt;code&gt;micro loop init&lt;/code&gt; drops the whole pipeline into any repository, and — the part that makes it real rather than aspirational — Go Micro itself now runs on it. The workflows that maintain this project are generated by the same command we&amp;rsquo;re shipping to you.&lt;/p&gt;</description></item></channel></rss>