<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on M1CH's Log</title><link>https://blog.m1ch.eu/tags/git/</link><description>Recent content in Git on M1CH's Log</description><generator>Hugo</generator><language>en-us</language><copyright>Michael Klamminger</copyright><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.m1ch.eu/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Conditional bootc build</title><link>https://blog.m1ch.eu/posts/20260507-forgejo-runneres-advanced/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://blog.m1ch.eu/posts/20260507-forgejo-runneres-advanced/</guid><description>&lt;p&gt;Running image builds on a schedule makes sense for security &amp;ndash; you want your bootc
images to pick up the latest Fedora updates automatically. But scheduling a daily
build that rebuilds every image every day, even when nothing upstream changed, wastes
runner time and fills the registry with identical layers.&lt;/p&gt;
&lt;p&gt;This post covers how I added upstream change detection to my Forgejo CI pipelines
for &lt;a href="https://codeberg.org/m1ch/gorgeOS"&gt;gorgeOS&lt;/a&gt;, so that scheduled builds are truly
no-ops when the upstream image hasn&amp;rsquo;t moved.&lt;/p&gt;</description></item><item><title>Bootc Matrix Build</title><link>https://blog.m1ch.eu/posts/20260505-bootc-matrix-build/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://blog.m1ch.eu/posts/20260505-bootc-matrix-build/</guid><description>&lt;p&gt;Running a Fedora-based bootc image stack means tracking multiple Fedora releases
in parallel. Instead of duplicating every job in the workflow, I wired up the
matrix strategy in Forgejo Actions to build F43 and F44 from a single job
definition.&lt;/p&gt;
&lt;h2 id="the-problem-with-hardcoded-versions"&gt;The Problem With Hardcoded Versions&lt;/h2&gt;
&lt;p&gt;Before, every Containerfile had a hardcoded base image:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-dockerfile" data-lang="dockerfile"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;FROM&lt;/span&gt; &lt;span style="color:#e6db74"&gt;git.m1ch.eu/oci/c-os:base-43&lt;/span&gt;&lt;span style="color:#960050;background-color:#1e0010"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Supporting F44 would have meant either duplicating the whole workflow or a manual
find-and-replace for every release. Neither scales.&lt;/p&gt;</description></item></channel></rss>