Comment on GitHub Has an Availability Problem. Is It Time to Look Elsewhere?

nixfreak@sopuli.xyz ⁨4⁩ ⁨days⁩ ago

• onlinepersona@programming.dev ⁨4⁩ ⁨days⁩ ago

  I’ve used. It works well enough. They supposedly have CI but either it’s not documented or nor ready, I can’t tell.

  And there’s no way to get notifications of merge requests, comments or anything actually, so it serves well as a backup or private project host, but not much else, IMO.

  original

  • PhenomenJan@lemmy.today ⁨3⁩ ⁨days⁩ ago

    I think it might just be that their documentation is dispersed, and sometimes hard to find. I haven’t used the CI, so I can’t comment on how well it works, but it appears to be in use: blog.liw.fi/posts/2026/radicle-status-quo-07/

    Here’s some docs on it: radicle-ci-broker.liw.fi/userguide.html radicle.network/…/rad%3AzwTxygwuz5LDGBq255RA2CbNG…

    original

    • onlinepersona@programming.dev ⁨2⁩ ⁨days⁩ ago

      Thanks for the links. Documentation is definitely a problem. They’d have to be open to feedback on documentation. Threads on documentation improvement are often met with “it exists, what more do you want?” even if the feedback is “this and this is missing” 🤷

      Anyway, I’ll check out the links and try to set something up. My usage of radicle is definitely what it could be because of the lack of notifications. I literally fire and forget my repos, patches and so on, because I haven’t found an easy way to be made aware of responses or incoming patches.

      original