<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Just Some Geek: git</title>
  <subtitle>Posts tagged with git</subtitle>
  <id>http://justsomegeek.com</id>
  <link href="http://justsomegeek.com"/>
  <link href="http://justsomegeek.com/tag/git/feed.xml" rel="self"/>
  <updated>2019-06-18T12:43:00+02:00</updated>
  <author>
    <name>m1n0</name>
  </author>
  <entry>
    <title>Empty GIT commit</title>
    <link rel="alternate" href="http://justsomegeek.com/2017/11/09/empty-git-commit/"/>
    <id>http://justsomegeek.com/2017/11/09/empty-git-commit/</id>
    <published>2017-11-09T10:53:00+01:00</published>
    <updated>2017-11-10T06:26:41+01:00</updated>
    <author>
      <name>m1n0</name>
    </author>
    <summary type="html"> Empty commits in git make sense is some scenarios, you might use them to trigger
workflows, builds, test commit hooks etc… 

 To create an empty commit, simply </summary>
  </entry>
  <entry>
    <title>Git&amp;#58; Cleaning up merged branches</title>
    <link rel="alternate" href="http://justsomegeek.com/2017/05/19/git-cleaning-up-merged-branches/"/>
    <id>http://justsomegeek.com/2017/05/19/git-cleaning-up-merged-branches/</id>
    <published>2017-05-19T08:07:00+02:00</published>
    <updated>2017-11-09T21:35:12+01:00</updated>
    <author>
      <name>m1n0</name>
    </author>
    <summary type="html"> Using some kind of git branching strategy (e.g. GitFLow, GitHub Flow or other) normally produces quite a lot of branches. When these do not get merged on you </summary>
  </entry>
</feed>
