<?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 Giedrius Statkevičius</title><link>https://giedrius.blog/categories/git/</link><description>Recent content in Git on Giedrius Statkevičius</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Oct 2018 20:15:55 +0000</lastBuildDate><atom:link href="https://giedrius.blog/categories/git/feed.xml" rel="self" type="application/rss+xml"/><item><title>Tutorial: Poor Man's Release/Shipping Process on GitLab</title><link>https://giedrius.blog/2018/10/01/tutorial-poor-mans-release-shipping-process-on-gitlab/</link><pubDate>Mon, 01 Oct 2018 20:15:55 +0000</pubDate><guid isPermaLink="false">https://giedrius.blog/?p=278</guid><description>&lt;p&gt;&lt;img alt="Image result for gitlab" loading="lazy" src="https://upload.wikimedia.org/wikipedia/commons/thumb/1/18/GitLab_Logo.svg/2000px-GitLab_Logo.svg.png"&gt;&lt;/p&gt;
&lt;p&gt;Since the recent acquisition of GitHub by Microsoft, a lot of people and companies are migrating to GitLab. The GitLab offering is especially attractive to early-stage start-ups since they offer free 10000 CI minutes or, in other words, 10000 minutes on their CI servers. It is easy to move over the workload to your own Kubernetes cluster once you run out of them - there is an easy-to-use user interface available where you could do that with just a few clicks.&lt;/p&gt;</description></item><item><title>Turbo-charging git-diff and making reviews easier</title><link>https://giedrius.blog/2018/07/23/turbo-charging-git-diff-and-making-reviews-easier/</link><pubDate>Mon, 23 Jul 2018 20:27:04 +0000</pubDate><guid isPermaLink="false">https://giedrius.blog/?p=221</guid><description>&lt;p&gt;&lt;img loading="lazy" src="https://git-scm.com/images/logos/downloads/Git-Logo-2Color.png"&gt;&lt;/p&gt;
&lt;p&gt;Are you working with git repositories in which a lot of code churn is happening? For example, do you have a repository with Puppet hierarchical data and there are a lot of pull requests where code is just being moved around between layers of hieradata? &lt;code&gt;diff(1)&lt;/code&gt; ordinarily only differentiates between added and removed lines with green and red colours (certainly the user controls what are actually those colours) however &lt;code&gt;git-diff(1)&lt;/code&gt; recently, at the end of 2017, got a new functionality where text that is just moved around can be highlighted in different colours. This is my case and this feature was a godsend because I did not want to spend a lot of time reviewing the syntax side of things if the hieradata is just being moved. That is why I wanted to share it with you so that it could help you out and perhaps someone has some even more good tips on how to make the reviewing process more effective.&lt;/p&gt;</description></item></channel></rss>