<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>7deeds &#187; git</title>
	<atom:link href="http://blog.7deeds.com/tag/git/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.7deeds.com</link>
	<description>Petros Amiridis - A humble programmer's seven noteworthy actions for the community</description>
	<lastBuildDate>Mon, 31 May 2010 12:09:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to enable VCS infromation in zsh</title>
		<link>http://blog.7deeds.com/2010/03/10/enable-vcs-infromation-in-zsh/</link>
		<comments>http://blog.7deeds.com/2010/03/10/enable-vcs-infromation-in-zsh/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 01:07:59 +0000</pubDate>
		<dc:creator>Petros</dc:creator>
				<category><![CDATA[tips]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[how-to]]></category>
		<category><![CDATA[self-note]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[zsh]]></category>

		<guid isPermaLink="false">http://blog.7deeds.com/?p=409</guid>
		<description><![CDATA[If you are using zsh as your terminal in Ubuntu, you can use a built in feature to display version control information at the prompt.
After reading &#8220;Zsh Prompt Magic&#8221; I created the zsh_vcs_info file which you can download. You place it in your home directory and open .zshrc and add the following line:

source /home/user/.zsh_vcs_info

Notice that [...]]]></description>
			<content:encoded><![CDATA[<p>If you are using zsh as your terminal in Ubuntu, you can use a built in feature to display version control information at the prompt.</p>
<p>After reading &#8220;<a href="http://kriener.org/articles/2009/06/04/zsh-prompt-magic">Zsh Prompt Magic</a>&#8221; I created the <a href='http://blog.7deeds.com/wp-content/zsh_vcs_info.zip'>zsh_vcs_info</a> file which you can download. You place it in your home directory and open .zshrc and add the following line:</p>
<pre class="brush: bash;">
source /home/user/.zsh_vcs_info
</pre>
<p>Notice that I added a . (dot) in the filename because I want it to be hidden. Also, notice that &#8220;user&#8221; in the path above, is the username of the account you use to log into Ubuntu.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.7deeds.com/2010/03/10/enable-vcs-infromation-in-zsh/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A typical workflow for a team using Git</title>
		<link>http://blog.7deeds.com/2009/08/27/typical-workflow-team-using-git/</link>
		<comments>http://blog.7deeds.com/2009/08/27/typical-workflow-team-using-git/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 13:28:43 +0000</pubDate>
		<dc:creator>Petros</dc:creator>
				<category><![CDATA[tips]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[ruby-on-rails]]></category>
		<category><![CDATA[self-note]]></category>

		<guid isPermaLink="false">http://blog.7deeds.com/?p=335</guid>
		<description><![CDATA[Lets assume you are in a team, working on a Rails project and you have chosen Git as your version control system. One way to complete a working cycle from pull to push is:
DISCLAIMER: There are more ways and many situations that are not described here. This is only a note to self that may [...]]]></description>
			<content:encoded><![CDATA[<p>Lets assume you are in a team, working on a Rails project and you have chosen Git as your version control system. One way to complete a working cycle from pull to push is:</p>
<p><em>DISCLAIMER: There are more ways and many situations that are not described here. This is only a note to self that may also be useful to you.</em></p>
<p><span id="more-335"></span></p>
<p><strong>Pull from your remote repository to make sure everything is up to date</strong></p>
<pre class="brush: bash; light: true;">git pull origin master</pre>
<p><strong>Create a new local branch for keeping your changes way from your local master branch</strong></p>
<pre class="brush: bash; light: true;">git branch my_new_feature</pre>
<p><strong>Switch to that branch and start working</strong></p>
<pre class="brush: bash; light: true;">git checkout my_new_feature</pre>
<p><strong>After finishing work and running successfully any cukes/specs/tests, commit</strong></p>
<pre class="brush: bash; light: true;">git commit -am &quot;Implemented my new super duper feature&quot;</pre>
<p><strong>Then, switch back to local master and pull if you need to also merge any changes since you first pulled</strong></p>
<pre class="brush: bash; light: true;">
git checkout master
git pull origin master
</pre>
<p><strong>Merge the local feature branch to master and run any cukes/specs/tests and if everything passes push changes</strong></p>
<pre class="brush: bash; light: true;">
git merge my_new_feature
git push origin master
</pre>
<p><strong>This is my preference: I delete the temporary local branch when everything is merged and pushed</strong></p>
<pre class="brush: bash; light: true;">git branch -d my_new_feature</pre>
<p>Update &#8211; Here is a more sophisticated approach: <a href="http://blog.hasmanythrough.com/2008/12/18/agile-git-and-the-story-branch-pattern">Agile git and the story branch pattern</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.7deeds.com/2009/08/27/typical-workflow-team-using-git/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Git log</title>
		<link>http://blog.7deeds.com/2009/08/25/git-log/</link>
		<comments>http://blog.7deeds.com/2009/08/25/git-log/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 15:25:28 +0000</pubDate>
		<dc:creator>Petros</dc:creator>
				<category><![CDATA[tips]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[self-note]]></category>

		<guid isPermaLink="false">http://blog.7deeds.com/?p=327</guid>
		<description><![CDATA[When I am working with git, I find it useful to take a quick look at the log. The default

$ git log

command doesn&#8217;t show the actual modified/added/deleted files. You can use the following command for that:

$ git log --pretty --stat

or

$ git log --pretty=format:&#34;[%h] %ae, %ar: %s&#34; --stat

I found the latter in one of Alex Young&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>When I am working with git, I find it useful to take a quick look at the log. The default</p>
<pre class="brush: bash; light: true;">
$ git log
</pre>
<p>command doesn&#8217;t show the actual modified/added/deleted files. You can use the following command for that:</p>
<pre class="brush: bash; light: true;">
$ git log --pretty --stat

or

$ git log --pretty=format:&quot;[%h] %ae, %ar: %s&quot; --stat
</pre>
<p>I found the latter in one of <a href="http://alexyoung.org/">Alex Young&#8217;s</a> tweets.</p>
<p>If you have any favorite git log formats, please feel free to mention them in a comment.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.7deeds.com/2009/08/25/git-log/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
