<story><title>GitHub Actions by Example</title><url>https://www.actionsbyexample.com/</url></story><parent_chain></parent_chain><comment><author>filleokus</author><text>GitHub Actions with act to test stuff locally is actually pretty usable. We use on-prem k8s-hosted runners to get access to servers&amp;#x2F;clusters with limited internet access, works great.&lt;p&gt;But as always with “”gitops”” themed tools I think it’s pretty awkward to handle rollbacks. Either you take the stance that master is the source of truth and let the CI&amp;#x2F;CD tooling revert commits if deployment fails, or you store that state elsewhere and allow e.g manifests to diverge from git.&lt;p&gt;I would be curious to hear how other people do it</text></comment>
<story><title>GitHub Actions by Example</title><url>https://www.actionsbyexample.com/</url></story><parent_chain></parent_chain><comment><author>keewee7</author><text>&amp;gt;Inspired by Go by Example&lt;p&gt;One of the best tutorials for people coming to Go from other languages:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gobyexample.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gobyexample.com&amp;#x2F;&lt;/a&gt;</text></comment>