<?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 Bryan Avery</title><link>https://bryanavery.co.uk/categories/git/</link><description>Recent content in Git on Bryan Avery</description><generator>Hugo -- gohugo.io</generator><language>en-GB</language><copyright>© 2026 Bryan Avery.</copyright><lastBuildDate>Mon, 26 Nov 2018 14:13:49 +0000</lastBuildDate><atom:link href="https://bryanavery.co.uk/categories/git/index.xml" rel="self" type="application/rss+xml"/><item><title>The best GIT GUI</title><link>https://bryanavery.co.uk/the-best-git-gui/</link><pubDate>Mon, 26 Nov 2018 14:13:49 +0000</pubDate><guid>https://bryanavery.co.uk/the-best-git-gui/</guid><description>&lt;p&gt;I have tried a number of Git GUI’s and the best by far has to the Source Tree&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://www.sourcetreeapp.com/" rel="noopener" target="_blank"&gt;https://www.sourcetreeapp.com/&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Why?    It’s just so easy to use and displays what you need when you need it.&lt;/p&gt;</description></item><item><title>Git Workflow</title><link>https://bryanavery.co.uk/git-workflow/</link><pubDate>Sun, 20 Aug 2017 15:40:08 +0000</pubDate><guid>https://bryanavery.co.uk/git-workflow/</guid><description>&lt;p&gt;Source control packages always have been a bit of a pain when you first start using them. You may know the principles of source control. Each environment has its own way and definitions and its own processes. Once you are used to using a source control system and the steps you follow it is easy. I call this the Source Control shuffle.&lt;/p&gt;</description></item></channel></rss>