<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>gitmerge &amp;mdash;   christova  </title>
    <link>https://christova.writeas.com/tag:gitmerge</link>
    <description>&lt;b&gt;&lt;h3&gt;Tech Articles&lt;/h3&gt;&lt;/b&gt;&lt;br/&gt;&lt;b&gt;Collated from various sources. Full copyright remains with original authors.&lt;/b&gt;</description>
    <pubDate>Wed, 06 May 2026 07:34:38 +0000</pubDate>
    <item>
      <title>Git Merge vs Git Rebase</title>
      <link>https://christova.writeas.com/git-merge-vs-git-rebase-zfjn?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[&#xA;&#xA;Git Merge vs. Rebase vs. Squash Commit! What are the differences?&#xA;&#xA;When we 𝐦𝐞𝐫𝐠𝐞 𝐜𝐡𝐚𝐧𝐠𝐞𝐬 from one Git branch to another, we can use ‘git merge’ or ‘git rebase’. The diagram above shows how the two commands work. &#xA;&#xA;𝐆𝐢𝐭 𝐌𝐞𝐫𝐠𝐞 &#xA;&#xA;This creates a new commit G’ in the main branch. G’ ties the histories of both main and feature branches. Git merge is 𝐧𝐨𝐧-𝐝𝐞𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐯𝐞. Neither the main nor the feature branch is changed. &#xA;&#xA;𝐆𝐢𝐭 𝐑𝐞𝐛𝐚𝐬𝐞 &#xA;&#xA;Git rebase moves the feature branch histories to the head of the main branch. It creates new commits E’, F’, and G’ for each commit in the feature branch. &#xA;&#xA;The benefit of rebase is that it has 𝐥𝐢𝐧𝐞𝐚𝐫 𝐜𝐨𝐦𝐦𝐢𝐭 𝐡𝐢𝐬𝐭𝐨𝐫𝐲. &#xA;&#xA;Rebase can be dangerous if “the golden rule of git rebase” is not followed. &#xA;&#xA;𝐓𝐡𝐞 𝐆𝐨𝐥𝐝𝐞𝐧 𝐑𝐮𝐥𝐞 𝐨𝐟 𝐆𝐢𝐭 𝐑𝐞𝐛𝐚𝐬𝐞 Never use it on public branches!&#xA;&#xA;#Git #git #gitmerge #gitrebase]]&gt;</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/uOTMkKEP.jpg" alt=""/></p>

<p>Git Merge vs. Rebase vs. Squash Commit! <strong>What are the differences</strong>?</p>

<p>When we 𝐦𝐞𝐫𝐠𝐞 𝐜𝐡𝐚𝐧𝐠𝐞𝐬 from one Git branch to another, we can use ‘git merge’ or ‘git rebase’. The diagram above shows how the two commands work.</p>

<p>𝐆𝐢𝐭 𝐌𝐞𝐫𝐠𝐞</p>

<p>This creates a new commit G’ in the main branch. G’ ties the histories of both main and feature branches. Git merge is 𝐧𝐨𝐧-𝐝𝐞𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐯𝐞. Neither the main nor the feature branch is changed.</p>

<p>𝐆𝐢𝐭 𝐑𝐞𝐛𝐚𝐬𝐞</p>

<p>Git rebase moves the feature branch histories to the head of the main branch. It creates new commits E’, F’, and G’ for each commit in the feature branch.</p>

<p>The benefit of rebase is that it has 𝐥𝐢𝐧𝐞𝐚𝐫 𝐜𝐨𝐦𝐦𝐢𝐭 𝐡𝐢𝐬𝐭𝐨𝐫𝐲.</p>

<p>Rebase can be dangerous if “the golden rule of git rebase” is not followed.</p>

<p>𝐓𝐡𝐞 𝐆𝐨𝐥𝐝𝐞𝐧 𝐑𝐮𝐥𝐞 𝐨𝐟 𝐆𝐢𝐭 𝐑𝐞𝐛𝐚𝐬𝐞 Never use it on public branches!</p>

<p><a href="https://christova.writeas.com/tag:Git" class="hashtag"><span>#</span><span class="p-category">Git</span></a> <a href="https://christova.writeas.com/tag:git" class="hashtag"><span>#</span><span class="p-category">git</span></a> <a href="https://christova.writeas.com/tag:gitmerge" class="hashtag"><span>#</span><span class="p-category">gitmerge</span></a> <a href="https://christova.writeas.com/tag:gitrebase" class="hashtag"><span>#</span><span class="p-category">gitrebase</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/git-merge-vs-git-rebase-zfjn</guid>
      <pubDate>Wed, 16 Oct 2024 09:57:41 +0000</pubDate>
    </item>
  </channel>
</rss>