<?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 Project Wintermute</title><link>https://wintermutecore.com/tags/github-actions/</link><description>Recent content in Github Actions on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Feb 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://wintermutecore.com/tags/github-actions/index.xml" rel="self" type="application/rss+xml"/><item><title>Speeding up GitHub Actions lint pipelines for large Go codebases</title><link>https://wintermutecore.com/posts/go-ci-lint-pipeline-optimisation/</link><pubDate>Thu, 12 Feb 2026 10:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/go-ci-lint-pipeline-optimisation/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Lint on a large Go monorepo went from 63 seconds to about 25 seconds on warm cache, with macOS skipped on branches. Five changes: concurrency group, conditional OS matrix, combined cache restore and save, explicit &lt;code&gt;go mod download&lt;/code&gt;, and incremental &lt;code&gt;golangci-lint --new-from-rev&lt;/code&gt;. None require a self-hosted runner.&lt;/p&gt;
&lt;p&gt;A large Go codebase makes the CI lint stage the part developers feel most: every push, on every branch. Lint feedback that takes a minute and a half kills iteration speed and quietly trains people to push less often, which is the opposite of what you want.&lt;/p&gt;</description></item></channel></rss>