<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Management on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/code-management/</link><description>Recent content in Code Management 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/code-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 2: Git and GitHub - Version Control for Collaboration</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/git-github-version-control/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/git-github-version-control/</guid><description>&lt;h2 id="chapter-2-git-and-github---version-control-for-collaboration"&gt;Chapter 2: Git and GitHub - Version Control for Collaboration&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 2 of our DevOps journey! In the previous chapter, you built a solid foundation with Linux fundamentals, mastering the command line, understanding file systems, and managing permissions. These skills are crucial because, in the world of DevOps, much of our work happens on Linux systems, and we interact with tools primarily through the terminal.&lt;/p&gt;
&lt;p&gt;Now, we&amp;rsquo;re ready to tackle a cornerstone of modern software development and DevOps: &lt;strong&gt;Version Control&lt;/strong&gt;. Specifically, we&amp;rsquo;ll dive deep into &lt;strong&gt;Git&lt;/strong&gt; and &lt;strong&gt;GitHub&lt;/strong&gt;. Imagine trying to build a complex project with a team without a way to track everyone&amp;rsquo;s changes, collaborate efficiently, or revert to a previous working state if something goes wrong. It would be chaos! Version control solves these very problems, making it indispensable for individual developers and large teams alike.&lt;/p&gt;</description></item><item><title>Building with Stacks: Effortlessly Managing Dependent Changes</title><link>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/building-with-stacks/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/building-with-stacks/</guid><description>&lt;h2 id="building-with-stacks-effortlessly-managing-dependent-changes"&gt;Building with Stacks: Effortlessly Managing Dependent Changes&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid Git explorer! In our previous chapters, you&amp;rsquo;ve embraced the power of GitButler&amp;rsquo;s virtual branches, discovering how they free you from the constraints of traditional Git workflows. You&amp;rsquo;ve learned to manage changes locally, creating and switching between isolated workstreams with ease.&lt;/p&gt;
&lt;p&gt;But what happens when your work isn&amp;rsquo;t so isolated? What if you&amp;rsquo;re building a large feature that needs to be broken down into several smaller, dependent changes? Or perhaps you&amp;rsquo;re working on a bug fix that requires a preliminary refactor. In traditional Git, this often leads to a tangled mess of &lt;code&gt;git rebase -i&lt;/code&gt; commands, complex pull requests, and the dreaded &amp;ldquo;merge conflict marathon.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>