Tweet by avenceslau

August 4, 2026

One thing that has annoyed me relentlessly in all of my cloudflare repos is CI CI always feels clunky and verbose, I have never had fun writing yaml and bash for CI I want to write rules once use them in all of my repos, reorder them, break them tear them apart It's integral to my dev flow, reuse, edit and replace. CI never felt good, I want to do things like find all deployables and preview, find all packages with changes and publish All of this things required more bash and more tooling than I cared to review and maintain and more yaml than what I want to read In a way, I am spoiled, @CloudflareDev's developer platform has for a while now allowed users to compose it's primitives into seamless dev experiences, and I have written CF code for years now, so any time I use something and it does not feel composable and extendable I cringe a little So for two months I have been running CI Workflows on all of my personal projects as a POC 1.5k lines of yaml dropped to 300 lines of TS, caching boundaries between jobs and between runs become obvious, you just add KV, if you can only run one release queue releases. It's the most fun I have had while writing CI and running CI Some of my repos had 5 jobs and in all of them I had to write the same exact yaml, now I have one workflow with all of the shared jobs, I run that first in every repo, and then for every custom job I just extend that workflow with the specific rules and behaviors There are a lot of things that I want to build first party support for, but for now I still need to properly understand the missing patterns, so tell us what we are missing so that we can work together on a fix

Author
avenceslau
Date
August 4, 2026
Open on X