<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitSnitch Blog</title><link>https://gitsnitch.app/blog/</link><description>Recent content on GitSnitch Blog</description><generator>Hugo</generator><language>en</language><copyright>GitSnitch</copyright><lastBuildDate>Fri, 18 Sep 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://gitsnitch.app/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is GitSnitch, and Why Would You Need It?</title><link>https://gitsnitch.app/blog/posts/what-is-gitsnitch/</link><pubDate>Fri, 18 Sep 2026 00:00:00 -0400</pubDate><guid>https://gitsnitch.app/blog/posts/what-is-gitsnitch/</guid><description>&lt;p&gt;If you&amp;rsquo;re reading this, there&amp;rsquo;s a decent chance you clicked through from somewhere like LinkedIn and have no idea what GitSnitch is yet. Fair enough. Here&amp;rsquo;s the plain version.&lt;/p&gt;&#10;&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;&#10;&lt;p&gt;Most security incidents on GitHub aren&amp;rsquo;t dramatic. Nobody breaks in through some clever exploit. What actually happens is much more boring:&lt;/p&gt;</description></item><item><title>Branch Protection Rules: What They Actually Protect You From</title><link>https://gitsnitch.app/blog/posts/branch-protection-rules/</link><pubDate>Thu, 17 Sep 2026 09:30:00 -0400</pubDate><guid>https://gitsnitch.app/blog/posts/branch-protection-rules/</guid><description>&lt;p&gt;Branch protection is one of those GitHub settings that quietly does its job in the background. Nobody notices it until it&amp;rsquo;s not there anymore, and by then something has usually already gone wrong.&lt;/p&gt;&#10;&lt;p&gt;If you run engineering, security, or you&amp;rsquo;re just the person who ends up on the hook when a repo gets compromised, this is worth five minutes.&lt;/p&gt;</description></item></channel></rss>