<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Git on Goatly.net</title>
    <link>https://www.goatly.net/categories/git/</link>
    <description>Recent content in Git on Goatly.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © Mike Goatly; all rights reserved.</copyright>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.goatly.net/categories/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>`gh stack rebase --no-trunk`: Reviewer-friendly rebasing for stacked PRs</title>
      <link>https://www.goatly.net/post/2026/09/gh-stack-rebase-no-trunk/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.goatly.net/post/2026/09/gh-stack-rebase-no-trunk/</guid>
      <description>
        
          
            &lt;blockquote&gt;
&lt;p&gt;TL;DR: &lt;code&gt;gh stack rebase --no-trunk&lt;/code&gt; is a reviewer friendly way to rebase your stacked PRs. Just as the blog title suggests.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Regarding GitHub stacked PRs: If you&amp;rsquo;ve already got someone reviewing a PR and they&amp;rsquo;ve requested changes, the temptation is to just do &lt;code&gt;gh stack rebase&lt;/code&gt; to get all your stacks updated again. Out of the box this has the side-effect of pulling an updated dev and rebasing the first branch on it.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
