<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Act - Tag - vo.rs</title><link>https://vo.rs/tags/act/</link><description>Act - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Fri, 13 Feb 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/act/" rel="self" type="application/rss+xml"/><item><title>Act: Running GitHub Actions Locally Before You Push</title><link>https://vo.rs/story/act-running-github-actions-locally-before-you-push/</link><description>&lt;p&gt;We have all done the thing. You tweak a workflow file, you can&amp;rsquo;t run it locally, so you push a commit called &amp;ldquo;fix ci&amp;rdquo;, watch it fail, push &amp;ldquo;fix ci 2&amp;rdquo;, fail, &amp;ldquo;actually fix ci&amp;rdquo;, fail, and by the time it&amp;rsquo;s green your git history reads like a cry for help. The feedback loop on GitHub Actions is dreadful precisely because the only way to test it is to use the production system itself, slowly, in public. &lt;code&gt;act&lt;/code&gt; fixes that by running your workflows locally in Docker.&lt;/p&gt;</description><pubDate>Fri, 13 Feb 2026 08:00:00 +0000</pubDate></item></channel></rss>