<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ken Warner on Medium]]></title>
        <description><![CDATA[Stories by Ken Warner on Medium]]></description>
        <link>https://medium.com/@kenwarner?source=rss-55301eeaedd4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Q5eMBFdPBFaD6tpx.jpeg</url>
            <title>Stories by Ken Warner on Medium</title>
            <link>https://medium.com/@kenwarner?source=rss-55301eeaedd4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:36:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kenwarner/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Command line UX matters too —Improve your git status colors]]></title>
            <link>https://medium.com/@kenwarner/command-line-ux-matters-too-improve-your-git-status-colors-170de858953d?source=rss-55301eeaedd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/170de858953d</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ken Warner]]></dc:creator>
            <pubDate>Sat, 06 Feb 2016 23:08:56 GMT</pubDate>
            <atom:updated>2016-02-06T23:08:56.289Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the first things I do when I set up a new development environment is to install git. However, the out-of-the-box color palette git uses has always left a lot to be desired, imo.</p><p>Good UX design uses color as a visual affordance to help us better understand at a glance the information being displayed and to help us act on that information more quickly and effectively. Just because we’re using a command line interface doesn’t mean we can’t take advantage of the same principles.</p><p>Fortunately, git allows us to <a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration#Colors-in-Git">customize our prompt</a> with our own colors! This capability has been around a long time, but I still see a lot of developers who either didn’t know, or didn’t realize the productivity boost you can get from it.</p><p>I spend the most time using the git status command, so let’s see what we can do. Here is an example of git’s default output color scheme using Windows Command Line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*iuiiTL_q8DNq-0mQ7Br1JQ.png" /><figcaption>Default git status colors using Windows Command Line</figcaption></figure><p>Green and red. One dimension of visual differentiation is nice, but otherwise it’s pretty meh. The red is a little hard to read against the black background too.</p><p>I prefer to use the PowerShell-based Git Shell that comes with <a href="https://desktop.github.com/">GitHub Desktop</a> anyways. Let’s see how it looks there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*3wdGmSRJShfBfuQz-UyP9g.png" /><figcaption>Default git status colors using GitHub Desktop Shell</figcaption></figure><p>Ok, now the red is really hard to read. Let’s see what we can do to improve it. Run the following commands in your terminal.</p><pre>git config --global color.status.header &quot;black normal bold&quot;<br>git config --global color.status.added &quot;green normal bold&quot;<br>git config --global color.status.updated &quot;green normal bold&quot;<br>git config --global color.status.changed &quot;yellow normal bold&quot;<br>git config --global color.status.untracked &quot;cyan normal bold&quot;<br>git config --global color.status.branch &quot;magenta normal bold&quot;<br>git config --global color.status.nobranch &quot;normal normal bold&quot;<br>git config --global color.status.unmerged &quot;red normal bold&quot;</pre><p>And now we have</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*38gmQq3ESFXL5hTXWdqg-Q.png" /><figcaption>Improved git status colors using Windows Command Line</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*V7c52YotOwHBmANMFh8fNg.png" /><figcaption>Improved git status colors using GitHub Desktop Shell</figcaption></figure><p>That’s more gooder!</p><p>But there’s still that dark red that’s hard to read in the PowerShell prompt git status text. Can we do anything about that? Yes, we can! GitHub’s Git Shell uses <a href="http://dahlbyk.github.io/posh-git/">PoshGit</a> which also provides a way to customize the colors used. GitHub installs this in the %USERPROFILE%\AppData\Local\GitHub folder. In it, look for a folder named PoshGit_somerandomlettersandnumbers and then a file named profile.example.ps1. I’ve added the following to that file, below the line Enable-GitColors.</p><pre>$global:GitPromptSettings.IndexForegroundColor = [ConsoleColor]::Green<br>$global:GitPromptSettings.WorkingForegroundColor = [ConsoleColor]::Red<br>$global:GitPromptSettings.UntrackedForegroundColor = [ConsoleColor]::Magenta<br>$global:GitPromptSettings.BranchAheadForegroundColor = [ConsoleColor]::Green<br>$global:GitPromptSettings.BranchBehindForegroundColor = [ConsoleColor]::Magenta</pre><p>If you want to know what else is possible, dig around in the GitPrompt.ps1 file in the same directory. There’s a few other places you can customize as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*nRcNq0VpwTRuUKFlSwP25w.png" /><figcaption>Even more improved git status colors using GitHub Desktop Shell</figcaption></figure><p>Looks pretty good. Now it’s time to go code!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=170de858953d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>