My particular use case is actually for a hobby/fun project
developing a bot in Rust to play a game (particularly, Screeps), and I want to track how fast it hits certain game thresholds with each newly developed feature. Gitea Actions for CI/CD, but it's all running on my local network/home lab so I'm happy to shift as needed.
Update
I'm trying Gitea Actions. There's still a little weirdness with some actions (e.g. the checkoutv3 action doesn't work if your git server has a path prefix like http://my.server/some_git_specific_prefix/[rest of normal path]), but overall it seems to be working nicely.
I'm currently running the act_runner daemon as a service on the bare raspberry pi/not in docker, since it has to interface with the docker socket anyway and there's no official act_runner docker image from gitea/I wouldn't be getting any "ease of update" benefits.
I didn't realize that gitea was adding actions either
it does look like their current setup expects the actions runner to be outside of docker, though: https://blog.gitea.io/2023/03/hacking-on-gitea-actions
That's not to say it would be impossible to wrap it in a container, but their claim that they "recommend running it on a separate server from the gitea server for performance reasons" makes me wonder if it'll work on my little pi.
10% more based on exchange rate
see comparisons here: https://steamdb.info/app/1716740/