<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workflow on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/workflow/</link><description>Recent content in Workflow on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>Welcome to GitButler: Revolutionizing Your Git Workflow</title><link>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/welcome-to-gitbutler/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/welcome-to-gitbutler/</guid><description>&lt;h2 id="welcome-to-gitbutler-revolutionizing-your-git-workflow"&gt;Welcome to GitButler: Revolutionizing Your Git Workflow&lt;/h2&gt;
&lt;p&gt;Hello and welcome to the exciting world of GitButler! If you&amp;rsquo;ve ever found yourself wrestling with &lt;code&gt;git rebase -i&lt;/code&gt;, managing multiple feature branches, or dreading the process of cleaning up your commit history, you&amp;rsquo;re in the right place. Git, while incredibly powerful, often presents a steep learning curve and can introduce friction into your daily development workflow.&lt;/p&gt;
&lt;p&gt;This chapter is your first step into understanding how GitButler aims to simplify and enhance your Git experience. We&amp;rsquo;ll explore its core philosophy, introduce the groundbreaking concepts of virtual and stacked branches, and get you set up with the application. By the end of this chapter, you&amp;rsquo;ll have GitButler installed and be ready to connect your first repository, setting the stage for a more efficient and enjoyable coding journey.&lt;/p&gt;</description></item><item><title>Setting Up Your Trigger.dev Environment &amp;amp; First Workflow</title><link>https://ai-blog.noorshomelab.dev/triggerdev-v4-guide-2026/setup-first-workflow/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/triggerdev-v4-guide-2026/setup-first-workflow/</guid><description>&lt;p&gt;Welcome to Chapter 2! In the previous chapter, we explored the &amp;ldquo;why&amp;rdquo; behind Trigger.dev, understanding its role in building robust, fault-tolerant AI agents and automated workflows. Now, it&amp;rsquo;s time to roll up our sleeves and dive into the &amp;ldquo;how.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;This chapter will guide you through setting up your local development environment for Trigger.dev v4-beta and creating your very first job. By the end, you&amp;rsquo;ll have a running Trigger.dev project, a basic understanding of its core components, and the satisfaction of seeing your first durable workflow execute. This hands-on experience is crucial for building confidence and understanding how Trigger.dev fits into your development stack.&lt;/p&gt;</description></item><item><title>Chapter 2: Setting Up Git and Your First Repository</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-2-setup-first-repo/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-2-setup-first-repo/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future Git master! In Chapter 1, we took a high-level flight over the world of Version Control Systems and understood &lt;em&gt;what&lt;/em&gt; Git is and &lt;em&gt;why&lt;/em&gt; it&amp;rsquo;s indispensable for modern development. Now, it&amp;rsquo;s time to roll up our sleeves and get practical.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to transform our theoretical understanding into hands-on experience. You&amp;rsquo;ll learn how to install Git on your machine, configure it to identify you as the author of your changes, and then take the monumental first step of initializing your very own local Git repository. This isn&amp;rsquo;t just about following instructions; it&amp;rsquo;s about building the fundamental environment where all your future version control magic will happen. Every line of code you write, every project you start, will begin with these foundational steps.&lt;/p&gt;</description></item><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><item><title>Chapter 5: Building Compression Plans: The OpenZL Workflow</title><link>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/05-compression-plans-workflow/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/05-compression-plans-workflow/</guid><description>&lt;h2 id="chapter-5-building-compression-plans-the-openzl-workflow"&gt;Chapter 5: Building Compression Plans: The OpenZL Workflow&lt;/h2&gt;
&lt;p&gt;Welcome back, aspiring data compression expert! In the previous chapters, we laid the groundwork for understanding OpenZL&amp;rsquo;s architecture and setting up our environment. Now, it&amp;rsquo;s time to dive into the heart of OpenZL: &lt;strong&gt;building and executing compression plans&lt;/strong&gt;. This is where OpenZL truly shines, allowing us to leverage its format-aware capabilities for superior compression of structured data.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll walk through the complete OpenZL workflow, from describing your data&amp;rsquo;s shape to training an optimized compression plan and then using it to compress and decompress your files. Understanding this workflow is crucial, as it&amp;rsquo;s the foundation for achieving the best possible compression ratios and speeds for your specific datasets. Get ready to put your knowledge into practice and see OpenZL in action!&lt;/p&gt;</description></item><item><title>Supercharging Development: VS Code and MCP Workflows</title><link>https://ai-blog.noorshomelab.dev/aipack-guide-2026/vscode-mcp-workflows/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/aipack-guide-2026/vscode-mcp-workflows/</guid><description>&lt;h2 id="supercharging-development-vs-code-and-mcp-workflows"&gt;Supercharging Development: VS Code and MCP Workflows&lt;/h2&gt;
&lt;p&gt;Welcome back, AI agent architects! In the previous chapters, we laid the groundwork for building and running your first AIPacks, exploring the core architecture and how to integrate various AI models. You&amp;rsquo;ve likely felt the power of agentic workflows, but perhaps also the challenges of observing and debugging them. How do you peer inside an agent&amp;rsquo;s mind to understand its decisions? How can you make your development process smoother and more integrated?&lt;/p&gt;</description></item><item><title>Advanced Workflows &amp;amp; Best Practices: Collaboration and AI Integration</title><link>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/advanced-workflows-best-practices/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/advanced-workflows-best-practices/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to the final chapter of our GitButler mastery guide! So far, you&amp;rsquo;ve learned the fundamentals of GitButler, from setting up your first repository to mastering virtual branches and local commit management. You&amp;rsquo;re now comfortable with its powerful UI and how it simplifies your individual Git workflow.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to level up your skills even further by diving into advanced workflows that truly shine in team environments and with emerging challenges like integrating AI-generated code. GitButler isn&amp;rsquo;t just a personal productivity tool; it&amp;rsquo;s a game-changer for collaboration, especially when dealing with complex feature development and stacked changes. We&amp;rsquo;ll explore how to leverage its unique capabilities to streamline pull request reviews, manage intricate dependencies, and even tame the often-messy output of AI coding assistants.&lt;/p&gt;</description></item><item><title>Optimizing Your Workflow: Customization and Productivity Hacks</title><link>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/customization-productivity/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/customization-productivity/</guid><description>&lt;p&gt;Welcome back, fellow Jujutsu explorers! You&amp;rsquo;ve mastered the core concepts of &lt;code&gt;jj&lt;/code&gt;, from its unique working-copy-as-a-commit model to navigating mutable history and leveraging the powerful operation log. Now, it&amp;rsquo;s time to truly make &lt;code&gt;jj&lt;/code&gt; your own.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll dive deep into customizing &lt;code&gt;jj&lt;/code&gt; to fit your personal workflow like a glove. We&amp;rsquo;ll explore configuration files, create powerful aliases for common commands, integrate &lt;code&gt;jj&lt;/code&gt; with your favorite editors and diff tools, and even craft custom output templates. The goal is simple: to make your &lt;code&gt;jj&lt;/code&gt; experience as efficient, intuitive, and productive as possible.&lt;/p&gt;</description></item><item><title>Migration, Best Practices, and The Future of Jujutsu</title><link>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/migration-best-practices-future/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/migration-best-practices-future/</guid><description>&lt;p&gt;Welcome to the final chapter of our Jujutsu journey! Throughout this guide, we&amp;rsquo;ve explored the foundational concepts of &lt;code&gt;jj&lt;/code&gt;, from its unique working-copy-as-a-commit model to its powerful mutable history and operation log. You&amp;rsquo;ve learned how &lt;code&gt;jj&lt;/code&gt; rethinks version control, offering a fresh perspective on common development challenges.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll consolidate your knowledge by diving into practical strategies for migrating existing Git projects to &lt;code&gt;jj&lt;/code&gt;. We&amp;rsquo;ll explore advanced best practices that truly unlock &lt;code&gt;jj&lt;/code&gt;&amp;rsquo;s potential in real-world scenarios, including insights for large projects and complex debugging. Finally, we&amp;rsquo;ll peer into the future of Jujutsu, discussing its ongoing development and potential impact on the version control landscape. By the end, you&amp;rsquo;ll have a holistic understanding of how to integrate &lt;code&gt;jj&lt;/code&gt; into your daily workflow and champion its unique advantages.&lt;/p&gt;</description></item><item><title>Jujutsu VCS: Zero-to-Mastery Guide</title><link>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/</guid><description>&lt;p&gt;This comprehensive guide offers a zero-to-mastery journey for Jujutsu (jj VCS), covering everything from initial installation and configuration to advanced real-world workflows. Developers will learn how to seamlessly integrate &lt;code&gt;jj&lt;/code&gt; into their daily routines, leveraging its unique features like mutable commits, operation logs, and branchless development for enhanced productivity. Explore Git interoperability, conflict resolution, stacked changes, and best practices to transform your software engineering workflow with &lt;code&gt;jj&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>GitButler Mastery Guide for Developers</title><link>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/</guid><description>&lt;p&gt;Welcome to the ultimate guide for mastering GitButler, the modern Git workflow tool. This collection of chapters will take you from a complete beginner to an advanced user, covering everything from basic setup and daily operations to complex branching strategies and collaborative features. Enhance your development workflow and streamline your Git experience with practical insights and expert tips.&lt;/p&gt;</description></item><item><title>GitButler Practical Field Guide</title><link>https://ai-blog.noorshomelab.dev/guides/gitbutler-mastery-guide/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/guides/gitbutler-mastery-guide/</guid><description>&lt;p&gt;This guide introduces &lt;strong&gt;GitButler&lt;/strong&gt;, a tool designed to simplify common challenges in Git workflows, particularly when managing multiple interdependent changes or reordering work. GitButler offers a visual approach to managing your local Git repository, aiming to streamline your development process.&lt;/p&gt;
&lt;p&gt;Throughout this guide, we will explore GitButler&amp;rsquo;s core concepts, such as virtual branches and stacked changes. The aim is to provide a clear understanding of both the practical use of the tool and the underlying principles that contribute to a more efficient development workflow. We will progress from fundamental concepts to advanced techniques, helping you integrate GitButler effectively into your daily work.&lt;/p&gt;</description></item><item><title>GitButler: The Revolution Git Needed, or Just a Smarter Assistant for 2026?</title><link>https://ai-blog.noorshomelab.dev/blog/gitbutler-modern-git-workflows-expert-analysis/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/blog/gitbutler-modern-git-workflows-expert-analysis/</guid><description>&lt;h2 id="beyond-the-git-commit---why-modern-devs-need-more"&gt;Beyond the &lt;code&gt;git commit&lt;/code&gt; - Why Modern Devs Need More&lt;/h2&gt;
&lt;p&gt;For over a decade, Git has been the undisputed monarch of version control. It&amp;rsquo;s powerful, flexible, and ubiquitous. Yet, any developer who&amp;rsquo;s navigated a complex rebase, juggled multiple in-progress features on different branches, or wrestled with a messy commit history knows that Git&amp;rsquo;s power often comes with a steep cognitive load. In a world accelerating towards AI-assisted coding and increasingly complex distributed teams, the traditional Git workflow can feel&amp;hellip; cumbersome.&lt;/p&gt;</description></item><item><title>Git Worktree Unlocked - Parallel Development Essentials</title><link>https://ai-blog.noorshomelab.dev/cut-the-chase/git-worktree-unlocked/</link><pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/cut-the-chase/git-worktree-unlocked/</guid><description>&lt;h1 id="git-worktree-unlocked---parallel-development-essentials"&gt;Git Worktree Unlocked - Parallel Development Essentials&lt;/h1&gt;
&lt;p&gt;Git Worktree enables multiple working directories, each connected to the same repository but checked out to a different branch, all sharing the core object database. Git 2.44.0+ (as of 2026-03-07).&lt;/p&gt;
&lt;h2 id="core-concept-the-multi-directory-model"&gt;Core Concept: The Multi-Directory Model&lt;/h2&gt;
&lt;p&gt;Traditionally, &lt;code&gt;git checkout&lt;/code&gt; changes your &lt;em&gt;entire&lt;/em&gt; working directory and index. Git Worktree breaks this by allowing multiple working directories, each with its own &lt;code&gt;HEAD&lt;/code&gt;, index, and working tree, all stemming from a single, shared &lt;code&gt;.git/objects&lt;/code&gt; store. This solves the problem of needing to stash or commit incomplete work when switching contexts.&lt;/p&gt;</description></item></channel></rss>