<?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 tigger.dev</title><link>https://tigger.dev/tags/git/</link><description>Recent content in Git on tigger.dev</description><generator>Hugo</generator><language>en-gb-oed</language><copyright>© Tadhg O'Brien</copyright><lastBuildDate>Sat, 23 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://tigger.dev/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Git Submodules with Local Overrides</title><link>https://tigger.dev/git-submodule-local-lib/</link><pubDate>Sat, 23 Aug 2025 00:00:00 +0000</pubDate><guid>https://tigger.dev/git-submodule-local-lib/</guid><description>&lt;div id="outline-container-headline-1" class="outline-2"&gt;
&lt;h2 id="headline-1"&gt;
Introduction
&lt;/h2&gt;
&lt;div id="outline-text-headline-1" class="outline-text-2"&gt;
&lt;p&gt;Managing your own libraries as Git submodules can be awkward: 
normally, you&amp;#39;d have to push and pull between different directories to keep
everything in sync. &lt;/p&gt;
&lt;p&gt;
But there&amp;#39;s a handy trick: keep the submodule pointing at your public remote
(for others who clone your project), while locally overriding the submodule&amp;#39;s
URL to use your &lt;strong&gt;own&lt;/strong&gt; local checkout. This way you get fast iteration, and
others still have a smooth experience.&lt;/p&gt;</description></item><item><title>Auto-Deploy Hugo from Github</title><link>https://tigger.dev/deploy-linode-github-actions/</link><pubDate>Sun, 16 Mar 2025 10:17:46 +0000</pubDate><guid>https://tigger.dev/deploy-linode-github-actions/</guid><description>&lt;p&gt;
GitHub is pretty good with &lt;a href="https://github.com/marketplace/actions/deploy-to-github-pages"&gt;out-of-box options for auto-deploying Hugo or Jekyll sites to GitHub Pages&lt;/a&gt;. But say you have your own VPS (e.g. Linode) - you can still take advantage of GitHub Actions which is a surprisingly versatile piece of CI/CD automation to rival anything you can do on the big cloud providers.&lt;/p&gt;
&lt;p&gt;
Or, if you just want to deploy to GitHub Pages, the out-of-box workflows that GitHub will create for you in the UI will hard-code a few things that you really don&amp;#39;t want hard-coded, such as the Hugo version (you always want to take advantage of the most recent dot-release, for security reasons if nothing else.) I have provided an example below that should remedy this issue.&lt;/p&gt;</description></item></channel></rss>