<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Commits on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/commits/</link><description>Recent content in Commits on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/commits/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering Your Changes: Interactive Commits and Local History Management</title><link>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/mastering-changes-interactive-commits/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/mastering-changes-interactive-commits/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future GitButler master! In our previous chapters, you&amp;rsquo;ve learned the magic of virtual branches and how they help you isolate your work. But what happens after you&amp;rsquo;ve made a bunch of changes on a virtual branch? Often, our initial coding spree results in a messy mix of refactors, new features, bug fixes, and maybe even a typo correction or two, all tangled together.&lt;/p&gt;
&lt;p&gt;This is where GitButler truly shines! This chapter is all about transforming that raw, unorganized work into a pristine, easy-to-understand commit history. We&amp;rsquo;ll dive deep into GitButler&amp;rsquo;s interactive tools that let you craft atomic commits, amend mistakes, reorder your work, and squash related changes – all without ever touching the dreaded &lt;code&gt;git rebase -i&lt;/code&gt; command line.&lt;/p&gt;</description></item></channel></rss>