Gitea "Actions disabled" (enable Actions in repo/admin) in CI

Gitea Actions is off by default at two levels: the instance ([actions] ENABLED in app.ini) and each repository (the Actions unit). If either is disabled, pushes create no runs.

What this error means

There is no Actions tab on the repo, or pushes never trigger a run. Admin has not enabled Actions in app.ini, or the repo has the Actions unit turned off.

Gitea

# Instance level: Actions not enabled in app.ini
# Repo level: Settings > Advanced Settings shows the "Actions" unit unchecked
[actions]
ENABLED = false

Common causes

Actions is disabled at the instance level

Without [actions] ENABLED = true in app.ini, the whole feature is off and no repo can run workflows.

The repository Actions unit is turned off

Even with the instance enabled, a repo whose Actions unit is unchecked will not surface an Actions tab or run workflows.

How to fix it

Enable Actions in app.ini and restart

Set [actions] ENABLED = true in Gitea app.ini.
Restart the Gitea service so the setting takes effect.
Confirm the Actions feature is now available.

app.ini

[actions]
ENABLED = true

Enable the Actions unit on the repository

In the repo Settings, enable the Actions unit so the tab appears and workflows run.

Gitea UI

# Repo > Settings > enable the "Actions" unit (Advanced Settings)

How to prevent it

Enable Actions in app.ini as part of instance provisioning.
Enable the Actions unit when creating repos that need CI.
Document the two-level toggle so new repos are not surprised.