<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #github</title>
    <link>/tags/github/</link>
    <description>Recent bookmarks tagged #github</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:42 +0000</lastBuildDate>
    <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>SSH access to Github over HTTPS | Jonathan Almeida</title>
      <link>https://jonalmeida.com/til/github-serves-ssh-over-tls-port/</link>
      <description>Host github.com&#xA;  HostName ssh.github.com&#xA;  Port 443&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #github #ssh #tips&lt;/p&gt;</description>
      <pubDate>Tue, 25 Aug 2026 23:39:09 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38714</guid>
      <category>github</category>
      <category>ssh</category>
      <category>tips</category>
    </item>
    <item>
      <title>withastro/triagebot-action: A GitHub Action for issue triage</title>
      <link>https://github.com/withastro/triagebot-action</link>
      <description>A GitHub Action for issue triage&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #agents #github #llms&lt;/p&gt;</description>
      <pubDate>Tue, 18 Aug 2026 17:57:05 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38692</guid>
      <category>agents</category>
      <category>github</category>
      <category>llms</category>
      <enclosure url="https://links.lmorchard.com/static/c3e544b5c7725f6befe9b421d92f5b5a.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Playwright on GitHub Actions: The setup that actually runs fast</title>
      <link>https://endform.dev/blog/playwright-github-actions</link>
      <description>This piece walks through that setup end to end. By the end you will know where your time is going, have a workflow that gives useful feedback on every PR, and know the point at which sharding actually becomes worth it.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ci #github #githubactions #playwright #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 14 Jul 2026 21:11:57 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38647</guid>
      <category>ci</category>
      <category>github</category>
      <category>githubactions</category>
      <category>playwright</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Using YAML frontmatter - GitHub Docs</title>
      <link>https://docs.github.com/en/contributing/writing-for-github-docs/using-yaml-frontmatter</link>
      <description>The following frontmatter values have special meanings and requirements for GitHub Docs. There&#39;s also a schema that&#39;s used by the test suite to validate every page&#39;s frontmatter. For more information, see lib/frontmatter.ts.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #docs #github #markdown #yaml&lt;/p&gt;</description>
      <pubDate>Sat, 30 May 2026 05:39:17 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38557</guid>
      <category>docs</category>
      <category>github</category>
      <category>markdown</category>
      <category>yaml</category>
    </item>
    <item>
      <title>docs/src/frame/lib/frontmatter.ts at main · github/docs</title>
      <link>https://github.com/github/docs/blob/main/src/frame/lib/frontmatter.ts</link>
      <description>The open-source repo for docs.github.com. Contribute to github/docs development by creating an account on GitHub.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #github #markdown #yaml&lt;/p&gt;</description>
      <pubDate>Sat, 30 May 2026 05:31:30 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38556</guid>
      <category>github</category>
      <category>markdown</category>
      <category>yaml</category>
      <enclosure url="https://links.lmorchard.com/static/0ed57b8e56e5901be0528a0999225cf6.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Self-hosted Forgejo Actions Runner – David Bushell – Web Dev (UK)</title>
      <link>https://dbushell.com/2025/08/15/self-hosted-forgejo-actions-runner/</link>
      <description>Did I mention GitHub is dead to me? I’m moving my code to a self-hosted Forgejo instance at git.dbushell.com. Today I added Actions.&#xA;&#xA;Forgejo Actions are a thing like GitHub Actions for “continuous integration”. Love a bit of CI! Forgejo Actions don’t work out of the box. You need to provide a “runner” which is a machine where all the action happens inside a containerised environment.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #actions #ci #forgejo #github&lt;/p&gt;</description>
      <pubDate>Tue, 05 May 2026 15:35:07 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38518</guid>
      <category>actions</category>
      <category>ci</category>
      <category>forgejo</category>
      <category>github</category>
      <enclosure url="https://links.lmorchard.com/static/b9ee58ea4a26b8203739b56bcfefa710.png" type="image/png"></enclosure>
    </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>Why there are no releases? · nvim-treesitter/nvim-treesitter · Discussion #8627</title>
      <link>https://github.com/nvim-treesitter/nvim-treesitter/discussions/8627</link>
      <description>&gt; So please, do go switch to something that doesn&#39;t require interacting with people.&#xA;&#xA;OK.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #community #github #oss&lt;/p&gt;</description>
      <pubDate>Tue, 07 Apr 2026 19:02:11 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38453</guid>
      <category>community</category>
      <category>github</category>
      <category>oss</category>
      <enclosure url="https://links.lmorchard.com/static/c8a27812141f912e63efcb426ef9bd5d.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>notes: copilot edited an ad into my pr</title>
      <link>https://notes.zachmanson.com/copilot-edited-an-ad-into-my-pr/</link>
      <description>After a team member summoned Copilot to correct a typo in a PR of mine, Copilot edited my PR description to include and ad for itself and Raycast.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #codegen #copilot #dev #github #oof&lt;/p&gt;</description>
      <pubDate>Tue, 31 Mar 2026 00:54:32 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38435</guid>
      <category>ai</category>
      <category>codegen</category>
      <category>copilot</category>
      <category>dev</category>
      <category>github</category>
      <category>oof</category>
    </item>
    <item>
      <title>Using Homebrew to Distribute Early Access Binaries from Private Github Repositories :: LGUG2Z</title>
      <link>https://lgug2z.com/articles/using-homebrew-to-distribute-early-access-binaries-from-private-github-repositories/</link>
      <description>After setting up nightly builds on GitHub Actions, I wanted to create a Homebrew Tap and Formula for people who sponsor me on GitHub for early access - being able to brew install is a much more pleasant onboarding experience for a new sponsor than having to compile from source.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #github #homebrew #macos&lt;/p&gt;</description>
      <pubDate>Mon, 27 Oct 2025 22:02:49 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37881</guid>
      <category>dev</category>
      <category>github</category>
      <category>homebrew</category>
      <category>macos</category>
      <enclosure url="https://links.lmorchard.com/static/986c3349c956b087148a893c24a2b515.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Running Pull Requests in Github Codespaces - These Yaks Ain’t Gonna Shave Themselves</title>
      <link>https://polotek.net/posts/running-pull-requests-in-github-codespaces/</link>
      <description>Here’s the idea. I have a solo project that I’m working on, and instead of hacking away on the main branch, I’m using a full feature branch and pull request workflow to keep my changes organized. This might seem like overkill, but it’s helpful for me because I tend to bounce around and leave things half done. I can run things locally and test different things by switching between branches. But I’m also doing a lot more AI-assisted development. Locally I use Claude Code. But I’ve been experimenting with allowing Github Copilot to create PRs. I create a github issue, assign it to copilot, and it spins up in the cloud and does work. Afterwards it opens a pull request for me to review. So even though this is a “solo” project, I end up with pull requests that I didn’t write myself and I need to validate.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #docker #github&lt;/p&gt;</description>
      <pubDate>Fri, 24 Oct 2025 23:23:09 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37858</guid>
      <category>dev</category>
      <category>docker</category>
      <category>github</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>github/spec-kit: 💫 Toolkit to help you get started with Spec-Driven Development</title>
      <link>https://github.com/github/spec-kit</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #codegen #github #llms #sdd&lt;/p&gt;</description>
      <pubDate>Mon, 08 Sep 2025 05:11:30 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:33310</guid>
      <category>ai</category>
      <category>codegen</category>
      <category>github</category>
      <category>llms</category>
      <category>sdd</category>
    </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>
  </channel>
</rss>
