<?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 Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/git/</link>
		<description>Recent content in Git on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 19 Oct 2026 12:10:35 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/git/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Git Merge vs Rebase: What Is the Difference?</title>
				<link>https://www.compilemymind.com/posts/git-merge-vs-rebase/</link>
				<pubDate>Mon, 19 Oct 2026 12:10:35 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/git-merge-vs-rebase/</guid>
				<description>&lt;p&gt;Your feature branch was current yesterday. This morning, &lt;code&gt;main&lt;/code&gt; has six new commits, the pull request shows a fork in the road, and someone says, “Just rebase it.” Someone else says, “Never rebase—merge is safer.”&lt;/p&gt;&#xA;&lt;p&gt;Both pieces of advice are incomplete.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Git merge joins histories without replacing the commits that already exist. Git rebase takes selected commits, replays their changes on a new base, and creates new commits.&lt;/strong&gt; Both can produce the same final files. They tell different stories about how those files arrived there.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
