<?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 jwogrady</title>
		<link>https://www.jwogrady.com/tags/git/</link>
		<description>Recent content in git on jwogrady</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 21 Sep 2026 21:02:54 -0500</lastBuildDate>
		
			<atom:link href="https://www.jwogrady.com/tags/git/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>A rebase keeps every byte and not one commit</title>
				<link>https://www.jwogrady.com/posts/the-only-copy/</link>
				<pubDate>Mon, 21 Sep 2026 21:02:54 -0500</pubDate>
				<guid>https://www.jwogrady.com/posts/the-only-copy/</guid>
				<description>&lt;p&gt;A repository had seventeen branches on the server and zero tags. Thirteen&#xA;tags existed on a laptop and on two older repositories that were due to be&#xA;retired. Pushing them up was housekeeping — the kind of thing you do&#xA;because it is free, not because you expect it to matter.&lt;/p&gt;&#xA;&lt;p&gt;The tags mark catalog snapshots, one per export of a plumbing company&amp;rsquo;s&#xA;price book, going back to the earliest known copy at eighty-seven services.&#xA;Nice to keep. Not urgent.&lt;/p&gt;</description>
			</item>
			<item>
				<title>I read one branch of six and called the salvage complete</title>
				<link>https://www.jwogrady.com/posts/one-branch-of-six/</link>
				<pubDate>Mon, 21 Sep 2026 20:57:28 -0500</pubDate>
				<guid>https://www.jwogrady.com/posts/one-branch-of-six/</guid>
				<description>&lt;p&gt;A repository was about to become the head of development for a customer&#xA;site, and everything it had been consolidated from was sitting in archives.&#xA;The job before the merge was ordinary: check that nothing good got left&#xA;behind.&lt;/p&gt;&#xA;&lt;p&gt;I did the careful version. Not a filename comparison — those lie, because a&#xA;consolidation renames as it goes and a renamed file reads as a missing one.&#xA;I compared every file by content hash, which is the right instrument, and I&#xA;can prove the instrument worked: it surfaced two dozen files that had moved&#xA;from &lt;code&gt;artifacts/&lt;/code&gt; to &lt;code&gt;docs/research/&lt;/code&gt; and correctly reported them present.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Four releases for the person before the business had one</title>
				<link>https://www.jwogrady.com/posts/personal-brand-first/</link>
				<pubDate>Mon, 21 Sep 2026 10:45:00 -0500</pubDate>
				<guid>https://www.jwogrady.com/posts/personal-brand-first/</guid>
				<description>&lt;p&gt;If you have ever gone back to something you wrote a few weeks ago about your&#xA;own plan, and found it describing a plan you no longer have —&lt;/p&gt;&#xA;&lt;p&gt;yes. That one. Let&amp;rsquo;s talk about that.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-i-would-have-told-you-yesterday&#34;&gt;What I would have told you yesterday&lt;/h2&gt;&#xA;&lt;p&gt;I have two Hugo themes. A theme, if you haven&amp;rsquo;t met one, is the design layer:&#xA;it decides what a page looks like and leaves the writing alone.&lt;/p&gt;</description>
			</item>
			<item>
				<title>I installed the theme and the theme did not appear</title>
				<link>https://www.jwogrady.com/posts/project-layouts-shadow-theme/</link>
				<pubDate>Sun, 20 Sep 2026 16:42:00 -0500</pubDate>
				<guid>https://www.jwogrady.com/posts/project-layouts-shadow-theme/</guid>
				<description>&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ git submodule add https://github.com/jwogrady/hugo-spectrum themes/hugo-spectrum&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Submodule rather than Hugo Modules, because Modules wants a &lt;code&gt;go.mod&lt;/code&gt; and this&#xA;theme doesn&amp;rsquo;t ship one. The submodule pins a commit, which means a checkout a&#xA;year from now builds the same site as today. I like that property a lot.&lt;/p&gt;&#xA;&lt;p&gt;Then I rebuilt and got my own handmade templates back.&lt;/p&gt;&#xA;&lt;p&gt;The scaffold &lt;code&gt;baseof.html&lt;/code&gt; and &lt;code&gt;page.html&lt;/code&gt; I&amp;rsquo;d written an hour earlier were&#xA;still sitting in &lt;code&gt;layouts/&lt;/code&gt;, and &lt;strong&gt;a project file at the same path beats the&#xA;theme&amp;rsquo;s entirely.&lt;/strong&gt; Not merged, not layered — replaced. Five files were&#xA;quietly overriding a theme I&amp;rsquo;d just installed, and the build was perfectly&#xA;happy about it.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
