I've published the April issue of the Radicle CI newsletter.
https://blog.liw.fi/posts/2026/radicle-status-quo-04/
#Radicle #RadicleCI #newsletter
cc @radicle
I've published the April issue of the Radicle CI newsletter.
https://blog.liw.fi/posts/2026/radicle-status-quo-04/
#Radicle #RadicleCI #newsletter
cc @radicle
I organize a weekly "office hour", for questions about Radicle CI, distributed CI, local-first CI, or related topics. Sometimes there's a demo or little presentation.
It's on Wednesdays, alternate weeks either morning (07 UTC ) or evening (16 UTC), in https://meet.ffmuc.net/radicleciofficehour (Jitsi, only needs browser, mic and webcam optional but helpful).
This week on Wednesday, April 15, at 16:00 UTC (18 CEST, 19 EST).
cc @radicle
@cehteh Super einfach... haha.
Jetzt hab ich ein Containerfile fΓΌr #Radicle geschrieben, weil es kein brauchbares Image gibt. π©
https://app.radicle.xyz/nodes/radicle.cytrinox.net/rad:z3EpMQhkkXbvHebwydHkBX3aKom8N
Lorenz Leutgeb: We got a new release of cypheraddr a few days ago, and I just rebased Patches > ec8bf7a2: #I2P Support. I encourage all the I2P enthusiasts to try it out ASAP, so that we can hopefully get some feedback before the next release from y'all.
Unfortunately, I can't hold a Radicle CI office hour this week.
Hey those who understand #radicle: how does one force push? I made a mistake in the commit message and pushed it to radicle. I then noticed my mistake, amended the commit and force pushed. This gave me a warning but succeeded otherwise. However, whenever I pull from the upstream, git ignores my force push and returns the local main branch back to the one with the typo. This is a private repo with my two machines as the delegates, a server allowed to sync it, and threshold 1.
Thanks in advance!