Live data from Hacker News

Radicle: Sovereign {code forge} built on Git

radicle.dev

11–20 of 101 posts

Re: Radicle: Sovereign {code forge} built on Git

#11
post #7

Radicle is really underrated, especially when working with agents. I find it a joy to use for my agentic workflows. If there's purely an agentic forge one day, it's likely going to be a distributed one, with cryptographic identities and signed artifacts by default.

AD: Feel free to post on our Zulip [^1] about your experiences of agentic workflow if you haven't already! Some of the team are interested in developing the agentic workflow experience.

[^1]: https://radicle.zulipchat.com/

Re: Radicle: Sovereign {code forge} built on Git

#12
post #2

The more I have been using git and building my own tooling and services around it for usage, I have figured out that something like radicle feels like the right/better solution, definitely better than what github is atm. There are rough edges and the seeding thing is a bit mehhh. And honestly there are a bunch of things I would do differently but I like the spirit of things. Not sure where the authors of the project…

AD: We're definitely interested in hearing about the rough edges and opinions! Feel free to post on our Zulip [^1] if you haven't already :).

[^1]: https://radicle.zulipchat.com/

Re: Radicle: Sovereign {code forge} built on Git

#13
post #7

Radicle is really underrated, especially when working with agents. I find it a joy to use for my agentic workflows. If there's purely an agentic forge one day, it's likely going to be a distributed one, with cryptographic identities and signed artifacts by default.

AD: Feel free to post on our Zulip [^1] about your experiences of agentic workflow if you haven't already! Some of the team are interested in developing the agentic workflow experience. [^1]: https://radicle.zulipchat.com/

"AD" ?

Re: Radicle: Sovereign {code forge} built on Git

#15

Earlier quoted context omitted.

AD: Feel free to post on our Zulip [^1] about your experiences of agentic workflow if you haven't already! Some of the team are interested in developing the agentic workflow experience. [^1]: https://radicle.zulipchat.com/

"AD" ?

Advertisement

Re: Radicle: Sovereign {code forge} built on Git

#17

Earlier quoted context omitted.

AD: Feel free to post on our Zulip [^1] about your experiences of agentic workflow if you haven't already! Some of the team are interested in developing the agentic workflow experience. [^1]: https://radicle.zulipchat.com/

"AD" ?

[deleted]

Re: Radicle: Sovereign {code forge} built on Git

#18

I like this idea a lot! I need to find people to try it with, though, which is not so easy with GH being so popular :-( Some nitpicks: * What is with the forced serif font on the website? * Does this support other version control systems? Like mercurial, SVN, pijul, etc.?

AD: The website is currently being redesigned, I suspect we'll have it up in the next few weeks. No it doesn't currently support other VCS's but we have planned for that possibility in future!

VCS agnosticism would be a selling point.

Re: Radicle: Sovereign {code forge} built on Git

#19

Earlier quoted context omitted.

AD: Feel free to post on our Zulip [^1] about your experiences of agentic workflow if you haven't already! Some of the team are interested in developing the agentic workflow experience. [^1]: https://radicle.zulipchat.com/

"AD" ?

His initials

Re: Radicle: Sovereign {code forge} built on Git

#20
post #8
post #6

How well does it hold up under load? What are the CI and PR stories?

Their CI take is early but promising: https://radicle-ci.liw.fi/

This just describes a watcher service that kicks jobs off on an external CI system and logs the results? Not much more detail than that.

Gitlab and Github have pages and pages going over the domain language used to configure the job triggers. Jobs can trigger other jobs either in response to completion or as a dependency etc etc.

I would say these radicle-ci designs as they are now are actually quite rudimentary. That's perfectly fine for an early project but at this point I think you have to say that they won't have a CI system ready for quite some time.

Post reply on HN