<?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 Dave Hogan</title>
    <link>https://davehogan.co.uk/tags/git/</link>
    <description>Recent content in Git on Dave Hogan</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 21 Aug 2024 23:44:22 +0100</lastBuildDate>
    <atom:link href="https://davehogan.co.uk/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rewriting Entire Git Branch into a Single Commit</title>
      <link>https://davehogan.co.uk/posts/development/rewriting-entire-git-repo-into-single-commit/</link>
      <pubDate>Wed, 21 Aug 2024 23:44:22 +0100</pubDate>
      <guid>https://davehogan.co.uk/posts/development/rewriting-entire-git-repo-into-single-commit/</guid>
      <description>&lt;h2 id=&#34;squishing-everything-back-to-a-single-commit-in-git&#34;&gt;Squishing Everything Back to a Single Commit in Git&lt;/h2&gt;
&lt;p&gt;Ever wanted your Git history to go back to the initial commit while preserving the content you have today? For example, maybe you&amp;rsquo;re making a private repository public and want to remove the commit history but keep the current state. While a better option might be to create a new repository and commit everything fresh, if you really need to do this, here are the steps I took recently.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Gitflow Branching Strategy</title>
      <link>https://davehogan.co.uk/posts/development/gitflow-branching-strategy/</link>
      <pubDate>Thu, 15 Aug 2024 16:41:46 +0100</pubDate>
      <guid>https://davehogan.co.uk/posts/development/gitflow-branching-strategy/</guid>
      <description>&lt;p&gt;&lt;em&gt;This post was taken from a rough &lt;a href=&#34;https://gist.githubusercontent.com/DaveHogan/77052a4bcd902d4242d5ccf86daa1ddd/&#34;&gt;gist&lt;/a&gt; I created whilst strategising a GitFlow branching strategy in a new team setting. Views may have likely changed since then and no on-size fits all.&lt;/em&gt;&lt;/p&gt;
&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;However you and your team manages branches; it&amp;rsquo;s important to have at least some kind of strategy that everyone adheres to. Rules and process should be designed to keep things consistent within the team and changes flowing to avoid complex merges and other such issues with multiple work steams on a single code repository.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
