<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Github on stuartleeks.com</title>
    <link>https://stuartleeks.com/tags/github/</link>
    <description>Recent content in Github on stuartleeks.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 May 2025 15:00:23 +0100</lastBuildDate>
    <atom:link href="https://stuartleeks.com/tags/github/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GitHub EntraID Federated Credentials With Merge Queue</title>
      <link>https://stuartleeks.com/posts/github-federated-credentials-merge-queue/</link>
      <pubDate>Thu, 08 May 2025 15:00:23 +0100</pubDate>
      <guid>https://stuartleeks.com/posts/github-federated-credentials-merge-queue/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;Huge thanks to &lt;a href=&#34;https://www.linkedin.com/in/maninderjitbindra/&#34;&gt;Mani&lt;/a&gt; for how to get this working!&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;I often have GitHub workflows that deploy resources to Azure.&#xA;In the past, I have created a service principal and use the client secret to authenticate to Azure.&#xA;This isn&amp;rsquo;t ideal as if the client secret is leaked then it can be used to access the Azure resources.&#xA;Additionally, the client secret needs to be rotated periodically which can be a pain (yeah, I&amp;rsquo;m lazy!).&lt;/p&gt;</description>
    </item>
    <item>
      <title>VS Code Dev Containers and Continuous Integration</title>
      <link>https://stuartleeks.com/posts/vscode-dev-containers-continuous-integration/</link>
      <pubDate>Thu, 08 Jul 2021 20:21:12 +0000</pubDate>
      <guid>https://stuartleeks.com/posts/vscode-dev-containers-continuous-integration/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;Visual Studio Code has a cool feature called &lt;a href=&#34;https://code.visualstudio.com/docs/remote/containers&#34;&gt;dev containers&lt;/a&gt; and I&amp;rsquo;ve &lt;a href=&#34;https://stuartleeks.com/tags/dev-containers/&#34;&gt;got a number of posts about them&lt;/a&gt; (and even included a chapter on them in my &lt;a href=&#34;https://wsl.tips/book&#34;&gt;book on Windows Subystem for Linux (WSL)&lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;Dev containers allow you to encapsulate the tools/dependencies that your project needs in a container image meaning you can replace the README steps for tool installation that you&amp;rsquo;d have to manually work through with a &lt;code&gt;Dockerfile&lt;/code&gt; that automates it. This makes it much quicker to onboard someone to your project, ensures consistent tooling across the team, and isolates tools in the container making it easier to work with different versions of tools across different projects.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fun with WSL, GitHub CLI and Windows Notifications</title>
      <link>https://stuartleeks.com/posts/wsl-github-cli-windows-notifications-part-2/</link>
      <pubDate>Thu, 27 May 2021 13:42:16 +0100</pubDate>
      <guid>https://stuartleeks.com/posts/wsl-github-cli-windows-notifications-part-2/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;In the &lt;a href=&#34;https://stuartleeks.com/posts/wsl-github-cli-windows-notifications-part-1/&#34;&gt;last post&lt;/a&gt; we saw how to create a drop-in replacement for &lt;code&gt;notify-send&lt;/code&gt;. This allowed us to take a script that used &lt;code&gt;notify-send&lt;/code&gt; and run it without modification. In this post, we&amp;rsquo;ll take a look at how we can update that script to take better advantage of Windows notifications.&lt;/p&gt;&#xA;&lt;p&gt;At the end of that post, the notification was fairly generic as shown below:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;./notification-previous.png&#34; alt=&#34;Notification with WSL Distro as category and &amp;ldquo;Run finished&amp;rdquo; as text&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fun with WSL, GitHub CLI and Windows Notifications</title>
      <link>https://stuartleeks.com/posts/wsl-github-cli-windows-notifications-part-1/</link>
      <pubDate>Thu, 27 May 2021 07:10:16 +0100</pubDate>
      <guid>https://stuartleeks.com/posts/wsl-github-cli-windows-notifications-part-1/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been making use of the &lt;a href=&#34;https://cli.github.com/&#34;&gt;GitHub CLI&lt;/a&gt; and finding it a productive way to work with GitHub. Recently, &lt;a href=&#34;https://blog.gripdev.xyz/&#34;&gt;Lawrence Gripper&lt;/a&gt; shared with me a handy alias that he had set up:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;alias ghrun&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;gh run list | grep \$(git branch --show-current) | cut -d&lt;/span&gt;$&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#39;\t&amp;#39; -f 8 | xargs gh run watch &amp;amp;&amp;amp; notify-send &amp;#39;Run finished&amp;#39;&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This &lt;code&gt;ghrun&lt;/code&gt; alias finds the latest GitHub actions workflow for the current branch and starts a &lt;code&gt;gh run watch&lt;/code&gt; for it. This shows the progress through the steps of a workflow:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
