Forgejo runner - alpha release, should not be considered secure enough to deploy in production
028451bf22
Since the `exec` command does not use labels from `.runner`, there is no existing way to specify which Docker image to use for task execution. This adds an `--image` flag for specifying it manually. The default remains `node:16-bullseye`. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Reviewed-on: https://gitea.com/gitea/act_runner/pulls/83 Reviewed-by: Jason Song <i@wolfogre.com> Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: telackey <telackey@noreply.gitea.io> Co-committed-by: telackey <telackey@noreply.gitea.io> |
||
|---|---|---|
| .forgejo/workflows | ||
| .gitea/workflows | ||
| artifactcache | ||
| client | ||
| cmd | ||
| config | ||
| core | ||
| engine | ||
| poller | ||
| register | ||
| runtime | ||
| .dockerignore | ||
| .gitignore | ||
| .golangci.yml | ||
| build.go | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| README.md | ||
Forgejo Actions runner
Runs workflows found in .forgejo/workflows, using a format similar to GitHub actions but with a Free Software implementation.
It is compatible with Forgejo v1.19.0-0-rc0