- Home
- Continuous Integration Software
- Forgejo Actions
On the recordRead 11 Oct 202615 facts
Forgejo Actions
Berlin, Germany
Plans and prices
Forgejo Actions
Free
Requires a Forgejo instance and a separately installed and configured runner
Read 11 Oct 2026 · forgejo.org
On the record
- Automatic token
- Each workflow receives a unique token that is destroyed when the workflow finishes and is limited to interactions with its repository.forgejo.org · read 11 Oct 2026
- Execution
- Forgejo does not run workflow jobs; a separately installed and configured Forgejo Runner fetches and executes them.forgejo.org · read 11 Oct 2026
- Feature availability
- Actions is enabled by default as of Forgejo v1.21, but an instance administrator can disable it.forgejo.org · read 11 Oct 2026
- 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.forgejo.org · read 11 Oct 2026
- Integrations
- Actions can use actions hosted on Forgejo, including actions served from a configurable default actions URL.forgejo.org · read 11 Oct 2026
- 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.forgejo.org · read 11 Oct 2026
- Purpose
- Forgejo Actions provides continuous integration driven by workflow files in a repository’s `.forgejo/workflows` directory.forgejo.org · read 11 Oct 2026
- Reusable workflows
- A workflow can call another workflow, and actions are reusable procedures used in CI workflows.forgejo.org · read 11 Oct 2026
- Runner choice
- Administrators can connect multiple runners to one Forgejo instance to distribute jobs across available compute resources.forgejo.org · read 11 Oct 2026
- Runner security
- Container runners provide isolation, but misconfiguration can allow escape; host runners have no real isolation.forgejo.org · read 11 Oct 2026
- Secrets
- Repository, user, and organization secrets are stored encrypted in the Forgejo database and made available to workflows.forgejo.org · read 11 Oct 2026
- Storage limits
- Job logs expire after a configurable delay that defaults to 365 days, and artifacts default to 90 days.forgejo.org · read 11 Oct 2026
- Triggers
- Workflows can be triggered by events including pushes, issues, pull requests, releases, schedules, and manual dispatches.forgejo.org · read 11 Oct 2026
