<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git-Optimization on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/git-optimization/</link><description>Recent content in Git-Optimization on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 11:17:39 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/git-optimization/index.xml" rel="self" type="application/rss+xml"/><item><title>Optimize git clone strategies to cut CI build times by up to 93%</title><link>https://curadevops.metacog.co.kr/insights/2026-08-19-avoid-the-massive-end-to-end-tax-of-default-full-history-clo/</link><pubDate>Wed, 19 Aug 2026 11:17:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-19-avoid-the-massive-end-to-end-tax-of-default-full-history-clo/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Relevant for teams self-hosting GitLab — shallow and partial clones reduce server-side pack-building load, which compounds as agentic workloads increase clone frequency. No operational change required today, but useful context for capacity planning.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Audit pipeline clone configurations and migrate to shallow (&lt;code>--depth=1&lt;/code>) or partial (&lt;code>--filter=blob:none&lt;/code>) clones; benchmarks show up to 93% time and 98% disk reduction per clone. No hard deadline, but AI-agent-driven clone volume makes this a near-term efficiency project worth scheduling this quarter.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>