The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service.
As Gitea is written in Go, it works across all the platforms and architectures that are supported by Go, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. This project has been forked from Gogs since November of 2016, but a lot has changed.
For online demonstrations, you can visit demo.gitea.com.
For accessing free Gitea service (with a limited number of repositories), you can visit gitea.com.
To quickly deploy your own dedicated Gitea instance on Gitea Cloud, you can start a free trial at cloud.gitea.com.
You can find comprehensive documentation on our official documentation website.
It includes installation, administration, usage, development, contributing guides, and more to help you get started and explore all features effectively.
If you have any suggestions or would like to contribute to it, you can visit the documentation repository
From the root of the source tree, run:
TAGS="bindata" make build
or if SQLite support is required:
TAGS="bindata sqlite sqlite_unlock_notify" make build
The build target is split into two sub-targets:
make backendwhich requires Go Stable, the required version is defined in go.mod.make frontendwhich requires Node.js LTS or greater and pnpm.
Internet connectivity is required to download the go and npm modules. When building from the official source tarballs which include pre-built frontend files, the frontend target will not be triggered, making it possible to build without Node.js.
More info: https://docs.gitea.com/installation/install-from-source
After building, a binary file named gitea will be generated in the root of the source tree by default. To run it, use:
./gitea web
Note
If you're interested in using our APIs, we have experimental support with documentation.
Expected workflow is: Fork -> Patch -> Push -> Pull Request
Note
- YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
- If you have found a vulnerability in the project, please write privately to security@gitea.io. Thanks!
Translations are done through Crowdin. If you want to translate to a new language, ask one of the managers in the Crowdin project to add a new language there.
You can also just create an issue for adding a language or ask on Discord on the #translation channel. If you need context or find some translation issues, you can leave a comment on the string or ask on Discord. For general translation questions there is a section in the docs. Currently a bit empty, but we hope to fill it as questions pop up.
Get more information from documentation.
We provide an official go-sdk, a CLI tool called tea and an action runner for Gitea Action.
We maintain a list of Gitea-related projects at gitea/awesome-gitea, where you can discover more third-party projects, including SDKs, plugins, themes, and more.
If you have questions that are not covered by the documentation, you can get in contact with us on our Discord server or create a post in the discourse forum.
Thank you to all our backers! 🙏 [Become a backer]
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
How do you pronounce Gitea?
Gitea is pronounced /ɡɪ’ti:/ as in "gi-tea" with a hard g.
Why is this not hosted on a Gitea instance?
We're working on it.
Where can I find the security patches?
In the release log or the change log, search for the keyword SECURITY to find the security patches.
This fork includes an AI Agent-optimized Robot API for automated issue management:
- PageRank Algorithm: Prioritizes issues based on dependency graph analysis
- Triage API:
GET /api/v1/robot/triage?owner=...&repo=... - Ready API:
GET /api/v1/robot/ready?owner=...&repo=... - Graph API:
GET /api/v1/robot/graph?owner=...&repo=... - CLI Tool:
cmd/gitea-robotfor command-line access
# Build CLI
go build -o gitea-robot ./cmd/gitea-robot
# Set environment variables
export GITEA_URL="http://localhost:3000"
export GITEA_TOKEN="your-api-token"
# Get prioritized issues
./gitea-robot triage --owner terraphim --repo gitea
# Get unblocked issues
./gitea-robot ready --owner terraphim --repo gitea
# Get dependency graph
./gitea-robot graph --owner terraphim --repo giteaMulti-architecture images are available from multiple registries:
# GitHub Container Registry (GHCR)
docker pull ghcr.io/terraphim/gitea:latest
docker pull ghcr.io/terraphim/gitea:rootless
# Gitea Registry
docker pull git.terraphim.cloud/terraphim/gitea:latest
docker pull git.terraphim.cloud/terraphim/gitea:rootlessTags available:
latest/1.26.0- Regular image (177 MB)rootless/1.26.0-rootless- Rootless image (160 MB)
To push images to GitHub Container Registry (GHCR):
# Authenticate with GitHub CLI (requires 'write:packages' scope)
gh auth token | docker login ghcr.io -u YOUR_USERNAME --password-stdin
# Build and tag
docker build -t ghcr.io/terraphim/gitea:latest .
docker build -t ghcr.io/terraphim/gitea:rootless -f Dockerfile.rootless .
# Push to GHCR
docker push ghcr.io/terraphim/gitea:latest
docker push ghcr.io/terraphim/gitea:rootlessTo publish to Gitea Registry:
# Login to Gitea Registry
docker login git.terraphim.cloud -u YOUR_USERNAME
# Build, tag, and push
docker build -t git.terraphim.cloud/terraphim/gitea:latest .
docker push git.terraphim.cloud/terraphim/gitea:latestFork-only references for the Robot API surface and the supporting agent tooling:
This project is licensed under the MIT License. See the LICENSE file for the full license text.
