<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Submodules on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/submodules/</link><description>Recent content in Submodules on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 11:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/submodules/index.xml" rel="self" type="application/rss+xml"/><item><title>Git Submodules: One Repository Pinned Inside Another</title><link>https://lab.artur-rios.tech/git/git-submodules/</link><pubDate>Wed, 21 Oct 2026 11:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/git/git-submodules/</guid><description>&lt;p&gt;This site is built with a Hugo theme I also maintain,&#10;&lt;a href="https://github.com/artur-rios/hugo-theme-nuno"&gt;nuno&lt;/a&gt;, and the theme lives in&#10;its own repository. The site needs an exact version of it, and I want to change&#10;the theme without copying files back and forth. Git&amp;rsquo;s answer is a&#10;&lt;strong&gt;submodule&lt;/strong&gt;: a repository placed inside another repository, the&#10;&lt;em&gt;superproject&lt;/em&gt;, which records exactly which commit of it to use. The site&amp;rsquo;s&#10;&lt;code&gt;themes/nuno&lt;/code&gt; folder is one, and it is the example throughout this article.&lt;/p&gt;</description></item></channel></rss>