<?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>GitHub on 🛠️ blog.yrhsk.work</title>
    <link>https://blog.yrhsk.work/tags/github/</link>
    <description>Recent content in GitHub on 🛠️ blog.yrhsk.work</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Apr 2026 08:08:45 +0300</lastBuildDate>
    <atom:link href="https://blog.yrhsk.work/tags/github/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why you should use GitHub repository rules instead of branch protection rules</title>
      <link>https://blog.yrhsk.work/posts/gh-repo-rules-instead-of-branch-protection-rules/</link>
      <pubDate>Wed, 22 Apr 2026 08:08:45 +0300</pubDate>
      <guid>https://blog.yrhsk.work/posts/gh-repo-rules-instead-of-branch-protection-rules/</guid>
      <description>&lt;p&gt;In July 2023, GitHub released a new feature called &lt;a href=&#34;https://github.blog/news-insights/product-news/github-repository-rules-are-now-generally-available/&#34;&gt;repository rules&lt;/a&gt;. I didn&amp;rsquo;t pay much attention to it at first, but then I faced multiple cases where branch protection rules felt like &amp;ldquo;something is missing&amp;rdquo;, and recently I decided to give repository rules (A.K.A. repository rulesets) a try.&lt;/p&gt;
&lt;p&gt;I was surprised by how much more flexible and powerful they are compared to traditional branch protection rules, so I wanted to share useful stuff about them, especially for those who haven&amp;rsquo;t heard of / tried repository rules yet.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
