<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #git</title>
    <link>/tags/git/</link>
    <description>Recent bookmarks tagged #git</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:46 +0000</lastBuildDate>
    <item>
      <title>Forgejo – Beyond coding. We forge.</title>
      <link>https://forgejo.org/</link>
      <description>Forgejo is a self-hosted lightweight software forge.&#xA;Easy to install and low maintenance, it just does the job.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #forgejo #git&lt;/p&gt;</description>
      <pubDate>Fri, 23 Oct 2026 00:15:19 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38818</guid>
      <category>dev</category>
      <category>forgejo</category>
      <category>git</category>
    </item>
    <item>
      <title>Don&#39;t couple your Go code to GitHub | Iain Cambridge</title>
      <link>https://iain.rocks/blog/dont-couple-your-go-code-to-github</link>
      <description>The main problem with using your git hosting location is that your code is now coupled to a hosting provider. That is, if you move your git hosting to GitLab then you have to change your code! Otherwise, you’ll be fetching the old verison. This can result in you being unable to change git hosting provider because the amount of overhead in switching. So you literally end up with your code coupled to GitHub. Which sounds completely nuts, but it’s something that is pretty much defacto in the Go community.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #git #github #go #golang&lt;/p&gt;</description>
      <pubDate>Mon, 28 Sep 2026 05:55:22 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38773</guid>
      <category>git</category>
      <category>github</category>
      <category>go</category>
      <category>golang</category>
    </item>
    <item>
      <title>GitHub is sinking – David Bushell – Web Dev (UK)</title>
      <link>https://dbushell.com/2026/04/29/github-is-sinking/</link>
      <description>GitHub is racing towards the mythical zero nines of uptime. Users are starting to notice that GitHub is now a Microsoft product. Eww!&#xA;&#xA;Official uptime paints a concerning chart. The missing status page tell a far worse story. Whatever the truth, it’s impossible to miss the delightful experience that is Microsoft GitHub if you use it semi-regularly.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #MSFT #git #github&lt;/p&gt;</description>
      <pubDate>Mon, 04 May 2026 16:48:33 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38517</guid>
      <category>MSFT</category>
      <category>git</category>
      <category>github</category>
      <enclosure url="https://links.lmorchard.com/static/87e3aa3016484be0f283a79cacff806b.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Radicle: the sovereign forge</title>
      <link>https://radicle.xyz/</link>
      <description>Radicle is an open source, peer-to-peer code collaboration stack built on Git. Unlike centralized code hosting platforms, there is no single entity controlling the network. Repositories are replicated across peers in a decentralized manner, and users are in full control of their data and workflow.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #coding #decentralized #git #p2p #tech&lt;/p&gt;</description>
      <pubDate>Sun, 18 Jan 2026 20:01:26 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38215</guid>
      <category>coding</category>
      <category>decentralized</category>
      <category>git</category>
      <category>p2p</category>
      <category>tech</category>
      <enclosure url="https://links.lmorchard.com/static/6bf88cd5c900870059b7956e3dea1a7b.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>git-pages/git-pages: Scalable static site server for Git forges (like GitHub Pages) - Codeberg.org</title>
      <link>https://codeberg.org/git-pages/git-pages</link>
      <description>git-pages is a static site server for use with Git forges (i.e. a GitHub Pages replacement). It is written with efficiency in mind, scaling horizontally to any number of deployed sites and concurrent requests and serving sites up to hundreds of megabytes in size, while being equally suitable for single-user deployments.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #git #hosting #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 12 Nov 2025 20:13:20 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37950</guid>
      <category>git</category>
      <category>hosting</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Grebedoc — static site hosting for git forges</title>
      <link>https://grebedoc.dev/</link>
      <description>In short: a service that publishes the pages branch in your Git repository as a website on your domain; think GitHub Pages if it was open source and community operated.&#xA;&#xA;More specifically, it is a public deployment of git-pages and Caddy configured to work especially with Codeberg but also with other Git forges. It is operated by Catherine &#39;whitequark&#39; and teammates, and currently deployed using Rage4 anycast infrastructure routing to VPSes in six regions (Europe, North America East, North America West, South America, East Asia, Australia), with site contents stored on Tigris and backed up to Wasabi.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #git #hosting #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 12 Nov 2025 20:12:50 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37949</guid>
      <category>git</category>
      <category>hosting</category>
      <category>webdev</category>
    </item>
    <item>
      <title>cdzombak/newt at dzombak.com</title>
      <link>https://github.com/cdzombak/newt?ref=dzombak.com</link>
      <description>Manage Git worktrees with ease. newt is a simple wrapper around Git worktrees that automatically organizes them in a .newt/ directory, provides merge status tracking, and handles deletion.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #git #worktrees&lt;/p&gt;</description>
      <pubDate>Thu, 30 Oct 2025 15:26:10 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37897</guid>
      <category>dev</category>
      <category>git</category>
      <category>worktrees</category>
    </item>
    <item>
      <title>You already have a git server: (Maurycy&#39;s blog)</title>
      <link>https://maurycyz.com/misc/easy_git/</link>
      <description>If you have a git repository on a server with ssh access, you can just clone it:&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #git #ssh&lt;/p&gt;</description>
      <pubDate>Mon, 27 Oct 2025 21:09:44 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37877</guid>
      <category>dev</category>
      <category>git</category>
      <category>ssh</category>
    </item>
    <item>
      <title>Simple automated deployments using git push</title>
      <link>https://garrido.io/notes/simple-automated-deployments-git-push/</link>
      <description>Using git push remains one of my favorite ways of deploying software. It’s simple, effective, and you can stretch it significantly until you need more complex workflows.&#xA;&#xA;I’m not referring to using git push to trigger a Github action which builds and deploys software. I’m talking about using git push web main to deploy your main branch to a server that you’ve named web.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #admin #git #sysadmin #webdev&lt;/p&gt;</description>
      <pubDate>Mon, 06 Oct 2025 21:50:08 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37782</guid>
      <category>admin</category>
      <category>git</category>
      <category>sysadmin</category>
      <category>webdev</category>
    </item>
    <item>
      <title>My self-hosted Forgejo runner setup | I do what I can</title>
      <link>https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-forgejo-runner-setup/</link>
      <description>In this (very long post) I will be demonstrating how I have setup my self-hosted Forgejo runners at home using Docker Compose, Docker-in-Docker and a bonus LXC. To demonstrate with a practical example, I will be building an Ansible Execution environment, to be used in my home lab automation. There will be two versions of it: a single node, and a dual node build. Both will result in the images for two platforms/architectures (AMD64 and ARM64).&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #forgejo #git #github #selfhosting&lt;/p&gt;</description>
      <pubDate>Wed, 01 Oct 2025 03:56:59 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37768</guid>
      <category>forgejo</category>
      <category>git</category>
      <category>github</category>
      <category>selfhosting</category>
      <enclosure url="https://links.lmorchard.com/static/6302d22d64033f6e01ed5c78a8311469.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>meks.quest</title>
      <link>https://meks.quest/blogs/the-theatre-of-pull-requests-and-code-review</link>
      <description>A key part of having a reviewable PR is writing commits that tell a story. Present your changes incrementally and logically so reviewers can follow your thought process. Generic commit messages such as &#34;add dependency,&#34; &#34;implement file upload feature,&#34; and &#34;address PR feedback&#34; don’t tell much of a story and leave reviewers guessing. Why was the dependency added? What were the specific steps in creating the file uploader feature? What feedback is being addressed?&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #coding #dev #git #work&lt;/p&gt;</description>
      <pubDate>Fri, 26 Sep 2025 00:44:21 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37755</guid>
      <category>coding</category>
      <category>dev</category>
      <category>git</category>
      <category>work</category>
    </item>
    <item>
      <title>Git exclude, a handy feature you might not know about / Marijke Luttekes</title>
      <link>https://marijkeluttekes.dev/blog/articles/2025/09/03/git-exclude-a-handy-feature-you-might-not-know-about/</link>
      <description>Exclude is particularly handy when you want to keep personal, non-standard files in a repository that is not yours, and where you cannot update its ignore files willy-nilly.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #git #tools&lt;/p&gt;</description>
      <pubDate>Wed, 17 Sep 2025 04:37:17 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37468</guid>
      <category>dev</category>
      <category>git</category>
      <category>tools</category>
      <enclosure url="https://links.lmorchard.com/static/bb0e89c77d86c2a901b059d3ff3eee3a.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Setting up cgit with Caddy v2 - SixFoisNeuf</title>
      <link>https://www.sixfoisneuf.fr/posts/setting-up-cgit-with-caddy2/</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #git #github&lt;/p&gt;</description>
      <pubDate>Mon, 08 Sep 2025 03:33:42 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:33306</guid>
      <category>dev</category>
      <category>git</category>
      <category>github</category>
    </item>
    <item>
      <title>cgit - A hyperfast web frontend for git repositories written in C.</title>
      <link>https://git.zx2c4.com/cgit/about/</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #cgi #git #tools #web&lt;/p&gt;</description>
      <pubDate>Mon, 08 Sep 2025 03:24:24 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:33305</guid>
      <category>cgi</category>
      <category>git</category>
      <category>tools</category>
      <category>web</category>
    </item>
    <item>
      <title>Modifying Other People&#39;s Software | natkr&#39;s ramblings</title>
      <link>https://natkr.com/2025-08-14-modifying-other-peoples-software/</link>
      <description>What if we could just.. import our patchset into Git, at the start of our session, and then export it back out as a series of patch files when we&#39;re done? That way we&#39;re effectively following the commandments of The Holy Quiltmother, but still get to keep our familiar Git UI.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #git #lappverk #patches #quilt #tools&lt;/p&gt;</description>
      <pubDate>Thu, 14 Aug 2025 20:36:46 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29376</guid>
      <category>dev</category>
      <category>git</category>
      <category>lappverk</category>
      <category>patches</category>
      <category>quilt</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
