<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Branch-Protection on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/branch-protection/</link><description>Recent content in Branch-Protection on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 12 Aug 2026 11:40:52 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/branch-protection/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub adds auto-migration from branch protection rules to rulesets</title><link>https://curadevops.metacog.co.kr/insights/2026-08-12-automatically-migrate-branch-protection-rules-to-repository/</link><pubDate>Wed, 12 Aug 2026 11:40:52 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-12-automatically-migrate-branch-protection-rules-to-repository/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> If your repos still use legacy branch protection rules, schedule migration to GitHub rulesets using the new in-settings converter — rulesets offer better scalability and cross-repo policy management with no hard deadline yet.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>