<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI/CD on Commentary of Takao</title><link>https://takao.blog/en/categories/ci/cd/</link><description>Recent content in CI/CD on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/categories/ci/cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Accelerating GitHub Actions Workflows via actions/cache</title><link>https://takao.blog/en/web/github-actions-caching-setup/</link><pubDate>Thu, 20 Nov 2025 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/github-actions-caching-setup/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Accelerating GitHub Actions Workflows via actions/cache" /&gt;&lt;p&gt;Automated CI/CD pipelines (like GitHub Actions) are a cornerstone of modern software quality control. However, if your workflows fetch external packages, boot container environments, and rebuild entire applications from scratch on every pull request, execution times can quickly balloon to several minutes.&lt;/p&gt;
&lt;p&gt;Long feedback loops slow developer productivity and lead to higher billing costs.&lt;/p&gt;
&lt;p&gt;In this article, we&amp;rsquo;ll demonstrate how to utilize GitHub&amp;rsquo;s official caching mechanisms to speed up your workflows from minutes to seconds.&lt;/p&gt;</description></item></channel></rss>