<?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 shocksolution.com</title><link>https://shocksolution.com/tags/git/</link><description>Recent content in Git on shocksolution.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 13 Aug 2011 21:57:14 +0000</lastBuildDate><atom:link href="https://shocksolution.com/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>A git branching strategy suitable for large projects</title><link>https://shocksolution.com/posts/a-git-branching-strategy-suitable-for-large-projects/</link><pubDate>Sat, 13 Aug 2011 21:57:14 +0000</pubDate><guid>https://shocksolution.com/posts/a-git-branching-strategy-suitable-for-large-projects/</guid><description>&lt;p&gt;Git is an amazing tool&amp;hellip;but what is the best way to use it?  Like any tool that gives you great power and flexibility, it&amp;rsquo;s up to you to use the tool in the best way to suit your purpose.  A friend of mine who manages an enterprise-class software development team recommended the &lt;a href="http://nvie.com/posts/a-successful-git-branching-model/" title="Git%20flow%20branching%20strategy"&gt;git branching strategy explained in this blog post&lt;/a&gt;.  I highly recommend reading it.&lt;/p&gt;</description></item></channel></rss>