Forgejo Actions
forgejo.org
- Free plan
- Linux
- Web
- API
- Self-hosted
What Forgejo Actions is
Forgejo Actions is a free, open-source continuous integration system built around workflow files in a repository’s `.forgejo/workflows` directory. Workflows can run for pushes, issues, pull requests, releases, schedules, or manual dispatches. One workflow can call another, and reusable actions provide procedures for CI jobs. Forgejo itself does not execute jobs: a separately installed and configured Forgejo Runner fetches and runs them. Administrators can connect multiple runners to distribute work across available compute resources. Repository, user, and organization secrets are encrypted in the Forgejo database. Each workflow receives a unique token that is destroyed after completion and limited to its repository. The system is designed to feel familiar to GitHub Actions users, but full compatibility is not promised, so workflows may need changes. Actions is enabled by default as of Forgejo v1.21, although an administrator can disable it. Job logs default to 365-day retention and artifacts to 90 days.
Who it suits
Forgejo Actions suits teams running self-hosted Forgejo instances who want repository-based CI workflows. It is intended for organizations seeking control over their own development platform.
Good to know, and what to watch
- Supports pushes, issues, pull requests, releases, and schedules
- Allows reusable workflows and actions
- Encrypts repository, user, and organization secrets
- Supports multiple runners for distributed jobs
- Provides repository-limited workflow tokens
- Requires a Forgejo instance
- Requires a separately installed and configured runner
- Full GitHub Actions compatibility is not promised
- Host runners have no real isolation
Plans
Every plan and priceForgejo Actions
Open source
The verdict
Forgejo Actions gives self-hosted Forgejo installations event-driven CI with encrypted secrets and flexible runner deployment. Setup and security depend on administrators managing the Forgejo instance and runners.
What the maker publishes
- Automatic token
- Each workflow receives a unique token that is destroyed when the workflow finishes and is limited to interactions with its repository. source
- Execution
- Forgejo does not run workflow jobs; a separately installed and configured Forgejo Runner fetches and executes them. source
- Feature availability
- Actions is enabled by default as of Forgejo v1.21, but an instance administrator can disable it. source
- Founded
- 2022 source
- GitHub Actions
- Forgejo Actions is designed to feel familiar to GitHub Actions users, but it does not claim full compatibility and workflows may need changes. source
- Headquarters
- Berlin, Germany source
- Integrations
- Actions can use actions hosted on Forgejo, including actions served from a configurable default actions URL. source
- Intended users
- Forgejo describes itself as a self-hosted lightweight software forge for people who want to host their own projects and control their development platform. source
- Purpose
- Forgejo Actions provides continuous integration driven by workflow files in a repository’s `.forgejo/workflows` directory. source
- Reusable workflows
- A workflow can call another workflow, and actions are reusable procedures used in CI workflows. source
- Runner choice
- Administrators can connect multiple runners to one Forgejo instance to distribute jobs across available compute resources. source
- Runner security
- Container runners provide isolation, but misconfiguration can allow escape; host runners have no real isolation. source
- Secrets
- Repository, user, and organization secrets are stored encrypted in the Forgejo database and made available to workflows. source
- Storage limits
- Job logs expire after a configurable delay that defaults to 365 days, and artifacts default to 90 days. source
- Triggers
- Workflows can be triggered by events including pushes, issues, pull requests, releases, schedules, and manual dispatches. source
Checked against the maker's pages on 11 Oct 2026.