<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pull Requests on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/pull-requests/</link><description>Recent content in Pull Requests 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/pull-requests/index.xml" rel="self" type="application/rss+xml"/><item><title>Integrating with Remote: Pushing Stacks and Preparing for Pull Requests</title><link>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/integrating-with-remote/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/integrating-with-remote/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, fellow developer! So far, we&amp;rsquo;ve explored the magic of GitButler locally, creating virtual branches, stacking changes, and managing our work with unparalleled flexibility. But what good is amazing local productivity if you can&amp;rsquo;t share it with your team? This chapter is all about bridging that gap.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll dive into how GitButler seamlessly integrates with your remote repositories. You&amp;rsquo;ll learn the crucial &amp;ldquo;Publish&amp;rdquo; action, which transforms your local virtual branch stacks into conventional Git branches on your remote. More importantly, we&amp;rsquo;ll guide you through the process of preparing these published branches for pull requests, embracing the powerful concept of &lt;em&gt;stacked pull requests&lt;/em&gt; that streamlines code review and collaboration.&lt;/p&gt;</description></item><item><title>Orchestrating Complex Tasks: Multi-Agent Workflows and Pull Request Automation</title><link>https://ai-blog.noorshomelab.dev/ai-coding-systems-2026/orchestrating-complex-tasks-multi-agent-workflows-pr-automation/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-coding-systems-2026/orchestrating-complex-tasks-multi-agent-workflows-pr-automation/</guid><description>&lt;h2 id="introduction-to-multi-agent-workflows"&gt;Introduction to Multi-Agent Workflows&lt;/h2&gt;
&lt;p&gt;Welcome to a pivotal chapter in our journey into AI-powered coding! So far, we&amp;rsquo;ve explored how AI copilots can significantly boost individual developer productivity through intelligent autocomplete, inline suggestions, and focused code generation. We&amp;rsquo;ve seen how tools like GitHub Copilot and Cursor IDE transform the coding experience from a passive editor into an active partner.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re taking a significant leap forward. We&amp;rsquo;ll move beyond simple assistive AI to the exciting realm of &lt;strong&gt;AI agent-based coding systems&lt;/strong&gt; and &lt;strong&gt;multi-agent workflows&lt;/strong&gt;. Imagine not just an AI suggesting your next line of code, but an AI that can understand a complex task, plan its execution, write substantial blocks of code, generate tests, update documentation, and even propose a Pull Request (PR) for human review—all with minimal intervention. This is the power of AI agents working in concert.&lt;/p&gt;</description></item><item><title>Chapter 10: Collaborative Development with Pull Requests on GitHub</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-10-pull-requests-github/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-10-pull-requests-github/</guid><description>&lt;h2 id="chapter-10-collaborative-development-with-pull-requests-on-github"&gt;Chapter 10: Collaborative Development with Pull Requests on GitHub&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our journey so far, you&amp;rsquo;ve mastered the foundational elements of Git: tracking changes, committing, branching, and pushing your work to a remote repository like GitHub. That&amp;rsquo;s a huge accomplishment! You can now manage your own projects and share your individual contributions.&lt;/p&gt;
&lt;p&gt;But what happens when you&amp;rsquo;re part of a team? How do multiple developers contribute to the same codebase without stepping on each other&amp;rsquo;s toes, introducing bugs, or creating chaos? This is where the magic of &lt;strong&gt;Pull Requests (PRs)&lt;/strong&gt; on platforms like GitHub comes into play.&lt;/p&gt;</description></item></channel></rss>