<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Git on W.P. Hill Tech</title>
    <link>https://wphilltech.com/tags/git/</link>
    <description>Recent content in Git on W.P. Hill Tech</description>
    <image>
      <title>W.P. Hill Tech</title>
      <url>https://wphilltech.com/static/papermod-cover.png</url>
      <link>https://wphilltech.com/static/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.140.2</generator>
    <language>en</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://wphilltech.com/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Blocking Commits and Pushes to Main With Native Git Hooks</title>
      <link>https://wphilltech.com/git-hooks-branch-protection/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wphilltech.com/git-hooks-branch-protection/</guid>
      <description>A follow-up to my Claude Code main-branch hook: git&amp;#39;s own native hook mechanism protects main for every git client on the machine, not just one AI tool. Why pre-commit catches the mistake early but has gaps, why pre-push is the backstop, and the pair I run on this site.</description>
    </item>
    <item>
      <title>Stopping Claude Code From Committing to Main</title>
      <link>https://wphilltech.com/claude-code-main-branch-protection/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wphilltech.com/claude-code-main-branch-protection/</guid>
      <description>I wanted a branch strategy where an AI coding agent can&amp;#39;t commit or push directly to main, but I still can. Here&amp;#39;s why GitLab branch protection doesn&amp;#39;t solve that, and the Claude Code hook that does.</description>
    </item>
  </channel>
</rss>
