When I tried this maybe a year ago, I couldn't get actions/cache to work. It looks like they merged support - but I had to make other act-only changes to my workflow to accommodate it. I wonder if that's improved since then? Can I just run my existing workflows, as is, using act now?

And, worse IMHO, Gitea is hitching their wagon to it https://gitea.com/gitea/act#forking-rules (plus whatever the relationship is to https://code.forgejo.org/forgejo/act#forking-rules ) and with all the marketing-speak about "runs github actions!" I think people are going to get a bad taste in their mouth from having improper expectations. I have the same bitterness from GitLab claiming that "gitlab-runner exec" does anything sane

My experience matches yours: it's a noble idea, but they have quite a way to go, including better error messages for when they assume something exists and doesn't. I do have a great deal of sympathy for the incredibly hard task of "run arbitrary JS from the Internet as if it were GitHub" but I'm also not the one who claims my tool runs arbitrary GitHub Actions yaml