Using Radicle CI

Re:Using Radicle CI by cedws on Wednesday July 23, 2025 @08:41PM (#44665624)

I have to disagree about Act, my experience is that it only works for extremely simple workflows, and even then it’s easy to run into differences between Act and GitHub Actions. I’ve raised many bugs but AFAIK there’s like one guy working on it in his own time.

It’s terrible that the community has had to invent something like this when it should be provided by GitHub. I suspect the GitHub Actions team is a skeleton crew because nothing ever seems to get done over there.

[ Parent | on HN ]

Re:Using Radicle CI by mdaniel on Wednesday July 23, 2025 @11:31PM (#44666593)

> AFAIK there’s like one guy working on it in his own time

That may very well be true of nektos/act itself, but it now has at least two (depending on how one counts such things) ongoing forks over in the Gitea and Forgejo projects as they foolishly try to squat on it instead of using a real CI tool

[ Parent | on HN ]

Re:Using Radicle CI by andrewaylett on Friday July 25, 2025 @10:14AM (#44683357)

I think we're in agreement, generally -- and GitHub have no incentive to help, because Actions are a moat and if it's too easy to run outside their environment then it's too easy to move away from their environment.

It's no shade on the author of Act (or on the quality of the code they've written) that they can't keep up with GitHub.

[ Parent | on HN ]