<?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 stuartleeks.com</title>
    <link>https://stuartleeks.com/tags/git/</link>
    <description>Recent content in Git on stuartleeks.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 03 Jul 2020 15:11:12 +0000</lastBuildDate>
    <atom:link href="https://stuartleeks.com/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Forwarding SSH Agent requests from WSL to Windows</title>
      <link>https://stuartleeks.com/posts/wsl-ssh-key-forward-to-windows/</link>
      <pubDate>Fri, 03 Jul 2020 15:11:12 +0000</pubDate>
      <guid>https://stuartleeks.com/posts/wsl-ssh-key-forward-to-windows/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;As I mentioned in my &lt;a href=&#34;https://stuartleeks.com/posts/git-for-windows-ssh-key-passphrases/&#34;&gt;previous post&lt;/a&gt;, I switched to using SSH key auth for GitHub and Azure DevOps Repos a long time ago and found it a positive experience. At first I was a bit lazy and didn&amp;rsquo;t use passphrases on my keys, and just kept a copy of my keys in the &lt;code&gt;.ssh&lt;/code&gt; folder in my User folder in Windows and another copy in &lt;code&gt;~/.ssh&lt;/code&gt; in WSL.&lt;/p&gt;&#xA;&lt;p&gt;For day-to-day working this worked okay, but I finally got round to adding passphrases to my keys a while back and was less happy with the setup at that point. My previously suppressed niggles around having the keys in multiple places re-surfaced once I had to add handle passphrases in multiple systems on the same machine!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fun with Git for Windows, SSH Keys and Passphrases</title>
      <link>https://stuartleeks.com/posts/git-for-windows-ssh-key-passphrases/</link>
      <pubDate>Tue, 30 Jun 2020 14:18:36 +0000</pubDate>
      <guid>https://stuartleeks.com/posts/git-for-windows-ssh-key-passphrases/</guid>
      <description>&lt;p&gt;Disclaimer: this post is one to file under &amp;ldquo;things I&amp;rsquo;m blogging in the hope that I find the answer more quickly next time&amp;rdquo;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;I switched to using SSH key auth for GitHub and Azure DevOps Repos a long time ago and never looked back. For a while I was using SSH keys without passphrases but got round to adding passphrases a while back. I set up the Windows OpenSSH Authentication Agent - the service defaults to Disabled so I set it as Automatic start and nudged it to Running. (For more information, see the &lt;a href=&#34;https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse&#34;&gt;docs on installing Windows OpenSSH&lt;/a&gt;)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Working With Git Rebase in Visual Studio Code</title>
      <link>https://stuartleeks.com/posts/working-with-git-rebase-in-visual-studio-code/</link>
      <pubDate>Thu, 23 Jan 2020 08:15:27 +0000</pubDate>
      <guid>https://stuartleeks.com/posts/working-with-git-rebase-in-visual-studio-code/</guid>
      <description>&lt;p&gt;Following the &lt;a href=&#34;https://stuartleeks.com/posts/setting-visual-studio-code-as-your-git-editor/&#34;&gt;git theme&lt;/a&gt; for mini-posts, I thought I&amp;rsquo;d give &lt;code&gt;git rebase&lt;/code&gt; a mention this time.&lt;/p&gt;&#xA;&lt;p&gt;When I first started working with git I found a way to pretend that it was a source control system like any other that I&amp;rsquo;d used. Eventually, I was working on a pull request for an OSS project and a maintainer asked me to rebase my changes. Now, I&amp;rsquo;d heard of rebase at that point but I hadn&amp;rsquo;t used it, so I was a bit daunted. So this post has a few tips that I wish I&amp;rsquo;d known at that point. By way of encouragement, I&amp;rsquo;ll add that getting familiar with git rebase is a huge part of the reason that I love git and has improved my developer workflow.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setting Visual Studio Code As Your Git Editor</title>
      <link>https://stuartleeks.com/posts/setting-visual-studio-code-as-your-git-editor/</link>
      <pubDate>Wed, 22 Jan 2020 07:17:34 +0000</pubDate>
      <guid>https://stuartleeks.com/posts/setting-visual-studio-code-as-your-git-editor/</guid>
      <description>&lt;p&gt;My &lt;a href=&#34;https://stuartleeks.com/posts/working-with-pull-requests-in-azure-devops/&#34;&gt;last post&lt;/a&gt; seemed to go down quite well, so I&amp;rsquo;m going to try a few mini-posts with a &lt;a href=&#34;https://stuartleeks.com/tags/tips-and-tricks&#34;&gt;&amp;rsquo;tips-and-tricks&amp;rsquo;&lt;/a&gt; theme. This works well for me as I&amp;rsquo;d started making some notes about productivity tips I use as part of my prep for an internal no-prep presentation ;-)&lt;/p&gt;&#xA;&lt;p&gt;This one is a really small tip that is covered in the &lt;a href=&#34;https://code.visualstudio.com/Docs/editor/versioncontrol#_vs-code-as-git-editor&#34;&gt;Visual Studio Code docs&lt;/a&gt;, but lots of people using Visual Studio Code seem to have missed it so I&amp;rsquo;m going to mention it here: you can set Visual Studio Code to be your git editor. To do this run:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
