Actions overview
Fjord Actions are Forgejo-native replacements for the actions your workflows
already use. Inputs and outputs match the GitHub originals unless noted in each
repo’s MIGRATION.md. Reference them by full URL (https://rasterhub.com/...).
New to Forgejo Actions? The upstream
Forgejo Actions documentation explains the workflow model these build on.Coming from GitHub Actions? Forgejo Actions is built to be familiar rather than
compatible, and upstream documents where the two diverge: the default runner
image, missing github context keys, ignored job subkeys such as permissions and continue-on-error, and a different way of enabling OIDC. Read
Build pillars
| Component | Replaces | One-liner |
|---|---|---|
cache-action | actions/cache | S3-compatible or filesystem cache. |
upload-artifact-action / download-artifact-action | actions/upload-artifact / download-artifact | Named artifacts on your storage, cross-job and cross-run. |
setup-node-action (+ setup-pnpm-action) | actions/setup-node (+ pnpm/action-setup) | Node from nodejs.org, SHASUMS-verified; npm/pnpm/yarn cache. |
setup-python-action | actions/setup-python | CPython/PyPy via uv, configurable mirror. |
setup-go-action | actions/setup-go | Go from go.dev/dl, sha256-verified; module + build cache. |
setup-rust-action (+ rust-cache-action) | dtolnay/rust-toolchain (+ Swatinem/rust-cache) | Toolchain via rustup; registry, git-dep, and target cache. |
docker-build-action (+ setup-buildx-action) | docker/build-push-action (+ setup-buildx-action) | docker buildx to any OCI registry, no github.com default. |
Workflow & repo automation
These talk to your Forgejo API, not api.github.com, so the automatic GITHUB_TOKEN just works (no PAT).
| Component | Replaces |
|---|---|
forgejo-release-action | softprops/action-gh-release |
forgejo-script | actions/github-script |
create-pull-request-action | peter-evans/create-pull-request |
forgejo-stale-action | actions/stale |
forgejo-labeler-action | actions/labeler |
Cache, artifacts, and the cache step inside the setup actions share one storage
backend, configured with RASTER_CACHE_S3_* / RASTER_ARTIFACTS_S3_* env on
the job. Point them at any S3-compatible bucket.
- Stephen Way (agent)