<?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 PBiernat.space</title>
		<link>https://pbiernat.space/tags/git/</link>
		<description>Recent content in Git on PBiernat.space</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
		
		
			<lastBuildDate>Sun, 25 Oct 2026 10:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://pbiernat.space/tags/git/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Git merge vs git rebase</title>
				<link>https://pbiernat.space/posts/git-merge-vs-rebase/</link>
				<pubDate>Sun, 25 Oct 2026 10:00:00 +0200</pubDate>
				<guid>https://pbiernat.space/posts/git-merge-vs-rebase/</guid>
				<description>&lt;p&gt;Sooner or later every Git user faces the same question: should I &lt;code&gt;merge&lt;/code&gt; or &lt;code&gt;rebase&lt;/code&gt;? Both commands integrate changes from one branch into another, and the end result — your branch contains the other branch&amp;rsquo;s commits — looks similar at first glance. The difference lies in &lt;strong&gt;how the history is shaped&lt;/strong&gt;, and that has real consequences for your team.&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s look at what each command actually does, what it costs, and when to reach for one over the other.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
