<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>git on Stewie</title><link>https://stewie1520.github.io/tags/git/</link><description>Recent content in git on Stewie</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 10 Nov 2026 00:00:00 +0700</lastBuildDate><atom:link href="https://stewie1520.github.io/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Rebasing a Stacked Branch After a Squash Merge</title><link>https://stewie1520.github.io/posts/git-rebase-onto/</link><pubDate>Tue, 10 Nov 2026 00:00:00 +0700</pubDate><guid>https://stewie1520.github.io/posts/git-rebase-onto/</guid><description>A situation that happens a lot in teams: a teammate opens feature-a, you need their work, so you branch feature-b off it and keep going. A few days later feature-a gets merged into main. Now you want feature-b to sit on top of main.
The obvious move doesn&amp;rsquo;t work You run git rebase main and&amp;hellip; conflicts. Lots of them, in code you never touched.
The reason: feature-a was squash-merged. Its 5 commits were combined into one brand-new commit S on main.</description></item></channel></rss>