CI for a Decentralized Forge: Why I Ended Up Bridging Radicle and Tekton

Thu, 09 Jul 2026 19:00:00 +0200

A few months ago I wrote about GitHub’s independence — short version, migrating from one centralized forge to another isn’t a strategy, it’s a rebrand. Recently I followed up with a review of Euro-Office and LaSuite, making the same point about European “sovereign” office suites being developed on GitHub. At the end of that article I promised I’d come back to this topic soon.

Here we are. This first post is about the why: why CI matters even when you’ve moved your git off the mainstream forges, why decentralizing CI is harder than decentralizing storage, and how I ended up picking Tekton after looking at some alternatives. The nuts and bolts of how the Radicle broker, my adapter, and the Tekton cluster talk to each other are worth their own write-up, and I’ll probably come back to them once the setup has more mileage.

Ci-Cd on Siryu

CI for a Decentralized Forge: Why I Ended Up Bridging Radicle and Tekton