<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Github Actions on Sander Knape</title>
    <link>https://sanderknape.com/tags/github-actions/</link>
    <description>Recent content in Github Actions on Sander Knape</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 13 Jan 2021 16:32:12 +0200</lastBuildDate>
    <atom:link href="https://sanderknape.com/tags/github-actions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go crazy with GitHub Actions</title>
      <link>https://sanderknape.com/2021/01/go-crazy-github-actions/</link>
      <pubDate>Wed, 13 Jan 2021 16:32:12 +0200</pubDate>
      <guid>https://sanderknape.com/2021/01/go-crazy-github-actions/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/features/actions&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;GitHub Actions&lt;/a&gt; is a component of GitHub that allows you to create automated workflows. Through the many different &lt;a href=&#34;https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;events&lt;/a&gt; that can trigger workflows you are free to build whatever automation you want. While the most common use case is building CI/CD pipelines, the possibilities are pretty much endless. Check out this list of &lt;a href=&#34;https://github.com/sdras/awesome-actions&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;awesome actions&lt;/a&gt; to get some inspiration.&lt;/p&gt;&#xA;&lt;p&gt;Having spent quite a bit of time with GitHub Actions in the last few months I came across some features that aren&amp;rsquo;t very well documented. It&amp;rsquo;s therefore very well possible that not everyone is familiar with these capabilities. Let&amp;rsquo;s dive into five neat features that you can go crazy with.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploy your pull requests with GitHub Actions and GitHub Deployments</title>
      <link>https://sanderknape.com/2020/05/deploy-pull-requests-github-actions-deployments/</link>
      <pubDate>Wed, 06 May 2020 12:49:31 +0200</pubDate>
      <guid>https://sanderknape.com/2020/05/deploy-pull-requests-github-actions-deployments/</guid>
      <description>&lt;p&gt;Performing (automated) tests on pull requests is a powerful mechanism to reduce the feedback loop on code changes. Known as &lt;a href=&#34;https://en.wikipedia.org/wiki/Shift-left_testing&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;shift left&lt;/a&gt;, the idea is that the earlier you find an issue with your code, the easier it is to fix it. For one, as you wrote the code recently it&amp;rsquo;s easier to get back into it. And of course, any code issue that doesn&amp;rsquo;t hit production is another potential issue for your end-users prevented.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Running self-hosted GitHub Actions runners in your Kubernetes cluster</title>
      <link>https://sanderknape.com/2020/03/self-hosted-github-actions-runner-kubernetes/</link>
      <pubDate>Mon, 16 Mar 2020 09:23:33 +0200</pubDate>
      <guid>https://sanderknape.com/2020/03/self-hosted-github-actions-runner-kubernetes/</guid>
      <description>&lt;p&gt;Last year November GitHub released &lt;a href=&#34;https://github.com/features/actions&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;GitHub Actions&lt;/a&gt;, a CI/CD solution build on top of GitHub&amp;rsquo;s Source Code Management. GitHub Actions is very convenient to use when your source code is already stored in GitHub as no additional tool is required for your CI/CD requirements. This blog is for example updated through a &lt;a href=&#34;https://github.com/SanderKnape/blog/blob/master/.github/workflows/publish.yml&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;GitHub Actions workflow&lt;/a&gt; whenever I push an update to my GitHub repository (like I just did with this post).&lt;/p&gt;&#xA;&lt;p&gt;Earlier this year GitHub released support for &lt;a href=&#34;https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;self-hosted runners&lt;/a&gt;. These runners run in your own infrastructure which has several advantages. Especially useful is the fact that these runners can access any private resources in your infrastructure such as staging environments for automated testing or secret/artifact management solutions not exposed publicly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
