<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci on Vegatron 🌈✨</title><link>https://vegatron.engineering/tags/ci/</link><description>Recent content in Ci on Vegatron 🌈✨</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 25 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vegatron.engineering/tags/ci/index.xml" rel="self" type="application/rss+xml"/><item><title>Linting Locally</title><link>https://vegatron.engineering/posts/linting-locally/</link><pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate><guid>https://vegatron.engineering/posts/linting-locally/</guid><description>&lt;p>Linting code on CI is a waste of resources.
Your time is better spent solving real problems.&lt;/p>
&lt;p>But you should lint your code.
It helps set a minimum standard.&lt;/p>
&lt;h1 id="ci-spinup">CI spinup&lt;/h1>
&lt;p>Spinning up CI instances is heavy and expensive.
They run noticably slower than your local machine.&lt;/p>
&lt;p>Think of all the steps &lt;em>before&lt;/em> linting: tooling, auth and, cloning.
You will pay for those resources while your engineer has an idle machine ready to work.&lt;/p></description></item></channel></rss>