<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Branch Management on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/branch-management/</link><description>Recent content in Branch Management on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 23 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/branch-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 8: The Power of Rebasing: Cleaner History, Smarter Merges</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-8-power-of-rebasing/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-8-power-of-rebasing/</guid><description>&lt;h2 id="chapter-8-the-power-of-rebasing-cleaner-history-smarter-merges"&gt;Chapter 8: The Power of Rebasing: Cleaner History, Smarter Merges&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our previous chapters, we mastered the basics of Git, learned how to create branches, and merged our work back into the main line of development. Merging is fantastic for combining divergent lines of work, but sometimes, the commit history can look a bit&amp;hellip; messy, full of extra merge commits.&lt;/p&gt;
&lt;p&gt;What if there was a way to integrate changes from one branch into another, but make it look like you developed your changes &lt;em&gt;directly&lt;/em&gt; on top of the latest version of the target branch? What if you could even tidy up your own commits &lt;em&gt;before&lt;/em&gt; sharing them with the world?&lt;/p&gt;</description></item></channel></rss>