<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Feature-Flags on Leading EDJE Blog</title><link>https://blog.LeadingEDJE.com/tags/feature-flags.html</link><description>Recent content in Feature-Flags on Leading EDJE Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Leading EDJE</copyright><lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.LeadingEDJE.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Gitflow Is a Legacy Trap</title><link>https://blog.LeadingEDJE.com/post/gitflow-legacy-trap.html</link><pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate><author>noreply@LeadingEDJE.com (Ben Grossman)</author><guid isPermaLink="true">https://blog.LeadingEDJE.com/post/gitflow-legacy-trap.html</guid><description>
Gitflow is now a legacy workflow that bakes unplanned merge work into your sprints. Here's why to drop it for trunk-based development.</description></item></channel></rss>