Forgejo Actions

What Forgejo Actions is

Forgejo Actions is a continuous integration system that uses workflow files in a repository’s `.forgejo/workflows` directory. Workflows can respond to pushes, issues, pull requests, releases, schedules, and manual dispatches; one workflow can also call another. Forgejo does not execute the jobs itself: a separately installed and configured Forgejo Runner fetches and runs them. Administrators can connect multiple runners to distribute jobs across available computing resources. Repository, user, and organization secrets are stored encrypted in the Forgejo database, and each workflow receives a unique token that is destroyed at completion and limited to its repository. The system is designed to feel familiar to GitHub Actions users, but compatibility is not complete and workflows may need changes. Actions can use hosted actions, including those at a configurable default URL. It is free and open source, but requires a Forgejo instance and runner. Actions is enabled by default as of Forgejo v1.21, though an administrator can disable it. Container runners offer isolation, but configuration matters; host runners have no real isolation.