<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Development &amp; Tools on Panic! At The Terminal</title>
		<link>https://blog.nousiainen.xyz/docs/development/</link>
		<description>Recent content in Development &amp; Tools on Panic! At The Terminal</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<atom:link href="https://blog.nousiainen.xyz/docs/development/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Resolving Git Submodule Tracking Issues</title>
				<link>https://blog.nousiainen.xyz/docs/development/git-submodule-tracking-issues/</link>
				<pubDate>Sat, 19 Jul 2025 21:30:00 +0300</pubDate>
				<guid>https://blog.nousiainen.xyz/docs/development/git-submodule-tracking-issues/</guid>
				<description>&lt;h1 id=&#34;resolving-git-submodule-tracking-issues&#34;&gt;&#xA;  Resolving Git Submodule Tracking Issues&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#resolving-git-submodule-tracking-issues&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;&#xA;  The Problem&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#the-problem&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;I recently encountered a frustrating Git issue with my Hugo blog setup. I had installed the &lt;a href=&#34;https://github.com/alex-shpak/hugo-book&#34;&gt;Hugo Book theme&lt;/a&gt; as a Git submodule for my static site, but for some reason there were a bunch of changed files showing up in the theme&amp;rsquo;s directory even though I had never run &lt;code&gt;git submodule update&lt;/code&gt; or made any intentional changes to it. At the time, I didn&amp;rsquo;t really understand how submodules work, so I tried adding it to &lt;code&gt;.gitignore&lt;/code&gt; thinking that would solve the problem.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How to Make a New Post on Hugo</title>
				<link>https://blog.nousiainen.xyz/docs/development/hugo-post/</link>
				<pubDate>Tue, 25 Mar 2025 18:32:04 +0200</pubDate>
				<guid>https://blog.nousiainen.xyz/docs/development/hugo-post/</guid>
				<description>&lt;h1 id=&#34;creating-new-posts-in-hugo&#34;&gt;&#xA;  Creating New Posts in Hugo&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#creating-new-posts-in-hugo&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;Hugo is a fast and flexible static site generator written in Go. Creating new posts is straightforward once you understand the basic workflow. This guide is mostly for myself since I don&amp;rsquo;t always remember how the process goes.&lt;/p&gt;&#xA;&lt;h2 id=&#34;step-by-step-process&#34;&gt;&#xA;  Step-by-Step Process&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#step-by-step-process&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;1-navigate-to-your-hugo-site-directory&#34;&gt;&#xA;  1. Navigate to your Hugo site directory&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#1-navigate-to-your-hugo-site-directory&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/var/lib/snapd/void/blog&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id=&#34;2-create-a-new-post-using-hugo-cli&#34;&gt;&#xA;  2. Create a new post using Hugo CLI&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#2-create-a-new-post-using-hugo-cli&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;hugo new content content/docs/hugo-post.md&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id=&#34;3-edit-the-post-content&#34;&gt;&#xA;  3. Edit the post content&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#3-edit-the-post-content&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;vim content/docs/hugo-post.md&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Edit the front matter (title, date, draft status) and add your content in Markdown.&lt;/p&gt;</description>
			</item>
			<item>
				<title></title>
				<link>https://blog.nousiainen.xyz/docs/development/powershell-vscode-precommit/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://blog.nousiainen.xyz/docs/development/powershell-vscode-precommit/</guid>
				<description>&lt;h1 id=&#34;automating-powershell-code-formatting-with-pre-commit-hooks&#34;&gt;&#xA;  Automating PowerShell Code Formatting with Pre-Commit Hooks&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#automating-powershell-code-formatting-with-pre-commit-hooks&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;&#xA;  The Problem&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#the-problem&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;If you&amp;rsquo;re working on a PowerShell project with multiple developers, you&amp;rsquo;ve probably experienced the pain of inconsistent code formatting. One developer uses tabs, another uses spaces. Braces are sometimes on the same line, sometimes on a new line. It&amp;rsquo;s a mess, and code reviews become debates about formatting instead of logic.&lt;/p&gt;&#xA;&lt;p&gt;VS Code&amp;rsquo;s PowerShell extension has a great &amp;ldquo;Format Document&amp;rdquo; feature, but let&amp;rsquo;s be honest—developers forget to use it.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
