GitHub Actions compatibility in Forgejo

Forgejo Actions is familiar, but compatibility is a migration plan, not a promise to skip testing.

Actions

What this solves

You are moving workflows from GitHub and need to estimate the porting work.

Best fit

GitHub to Forgejo migrations
Runner label reviews
Action replacement planning

How to think about it

The YAML shape is familiar, but real compatibility depends on runner labels, network access, secrets, third-party actions, artifacts, caches, and assumptions about GitHub-hosted services. Treat the first workflow as a rehearsal for the whole migration.

Compatibility review

jobs:
  test:
    runs-on: docker
    steps:
      - uses: actions/checkout@v4
      - run: env | sort
      - run: ./scripts/test.sh

Practical path

01 Inventory third-party actions and hosted-runner assumptions.
02 Replace GitHub-hosted dependencies with reachable Forgejo equivalents.
03 Run one representative workflow before scheduling cutover.

When to choose another path

Inventory every `uses:` reference before migration.

Check whether actions are reachable from your runner network.

Replace GitHub-specific tokens, APIs, and hosted-runner assumptions.

Next resources

Actions docs

Forgejo Actions on Fjord.

CI migration guide

Port workflows from GitHub or GitLab.

Runner sizing

Check operational readiness.

Managed hosting

Dedicated Forgejo with operated runners.