Gitea Actions is the built-in continuous integration and delivery engine of Gitea, the lightweight self-hosted Git forge. It is compatible with GitHub Actions workflow syntax, so workflows defined in .gitea/workflows/*.yml run jobs and steps on Gitea Runners, letting you keep CI inside the same platform that hosts your repositories without a separate build service.

Key Features

• GitHub Actions compatible — reuse familiar workflow, job, step, and event syntax.
• Integrated with Gitea — activate Actions per repository with no extra external CI service.
• Pluggable runners — Gitea Runners (act-based) execute jobs and can be scaled to taste.
• Workflow files in-repo — define pipelines in .gitea/workflows/*.yml, versioned with your code.
• Rich events — trigger on push, pull request, schedule, tags, and more.
• Secrets & variables — manage encrypted secrets and configuration variables per repository or organisation.
• Matrices & concurrency — run jobs across multiple images and control parallel execution.
• Live logs & status — view job steps and streams of runner output in the Gitea UI.

Why Use Gitea Actions?

If you already self-host with Gitea, Actions removes the need for a separate CI/CD application. Because it speaks the GitHub Actions workflow format, teams migrating from GitHub can bring their pipelines over largely unchanged, and everything stays on your own hardware.

Use Cases

• Continuous integration for repositories hosted on a self-hosted Gitea forge.
• Migrating GitHub Actions workflows to an entirely self-hosted platform.
• Build, test, and container packaging automated within the same Git interface.
• Lightweight CI/CD for teams that want a single, simple self-hosted toolchain.

Platform

Self-hosted (Go) · Linux · Windows · macOS · Docker

Licence

MIT License (Gitea)

Website

docs.gitea.com/usage/actions