<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github-Action on iqbalsyamil</title><link>https://iqbalsyamil.com/tags/github-action/</link><description>Recent content in Github-Action on iqbalsyamil</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://iqbalsyamil.com/tags/github-action/index.xml" rel="self" type="application/rss+xml"/><item><title>Caching Your Way to Faster CI Runners</title><link>https://iqbalsyamil.com/posts/caching-your-way-to-faster-ci-runners/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://iqbalsyamil.com/posts/caching-your-way-to-faster-ci-runners/</guid><description>I maintained CI Platform at a company running a Go monorepo with trunk-based development, more than 100 services, and over 100 engineers pushing code every day. CI runs on EKS with GitHub Actions Runner Controller. For a long time the feedback I kept hearing from engineers was &amp;ldquo;CI is slow&amp;rdquo; and the feedback from finance was &amp;ldquo;the bill keeps going up.&amp;rdquo; Neither is actionable on its own.
This post covers the startup optimizations we shipped and why we made the decisions we did.</description></item></channel></rss>