Gitea (@giteaio) header
Gitea (@giteaio) profile picture

Git with a cup of tea! Painless self-hosted all-in-one software dev service. Includes Git hosting, code review, team collaboration, package registry and CI/CD

Earth
Joined December 2016
Photo by Gitea (@giteaio)Photo by Gitea (@giteaio)Photo by Gitea (@giteaio)Photo by Gitea (@giteaio)Photo by Gitea (@giteaio)Photo by Gitea (@giteaio)Photo by Gitea (@giteaio)Photo by Gitea (@giteaio)
Pinned Tweet
Gitea 28.3.0 is here! 🎉 This maintenance release fixes multiple security issues and improves performance across Actions, issues, pull requests, and packages. Upgrading is strongly recommended. Read the full release notes: blog.gitea.com/release-of-28… #Gitea #OpenSource #SelfHosted
2
14
3
98
4,740
Every pull request in my home lab now gets an AI code review, and the diff never leaves my network. No seat fees, no hosted model, and every verdict comes from code I can read. How it works: 1. gitleaks blocks secrets at commit time, before anything is pushed. 2. Gitea opens the pull request and hands it to act_runner on the same box. 3. Luddite Scout runs static pre-flight checks (agent instruction files, hidden Unicode, workflows, lockfiles, build scripts) and fails the check on a high finding. 4. coderev reviews the diff. A generator model proposes findings, three skeptic seats try to refute each one, and only the survivors post as a single comment with inline notes. Three Omarchy machines do all of it. The Omarchy Laptop is where I commit. The Omarchy Server runs Gitea, the runner, PostgreSQL, Traefik and LiteLLM. The Omarchy Desktop's RTX 3090 runs Ollama. The model path: coderev calls LiteLLM, and LiteLLM routes to Ollama on the Omarchy Desktop. The main review uses Qwen3-Coder 30B (3.3B active parameters). New today: adding a review:all-models label to a pull request runs coderev once per local model, ten of them, each tagged with the largest context that fits the 24 GB card without spilling to CPU, from 56K to 256K tokens. Each model acts as generator and panel and posts its own comment. The jobs run one after another so only one model is loaded at a time. The lab also runs a coderev build with hidden-Unicode detection, which is an open PR upstream. Bidi controls, tag characters and zero-width marks are found by plain code before any model sees the diff, then escaped on every route to the model, so text a reviewer cannot see never reaches the model unmarked. Across three of my PRs today, the main review posted 10 findings and 9 were wrong. A local 30B model is noisy, so the AI review stays advisory and never blocks a merge. The hard gates are the deterministic ones. Every action is pinned to a commit SHA. Built entirely on open source: Gitea, the forge @giteaio github.com/go-gitea/gitea Gitea runner, the CI gitea.com/gitea/runner coderev, AI review with a refutation panel @btsouth github.com/btsouth/coderev LiteLLM, the model gateway @litellm github.com/BerriAI/litellm Ollama, local inference @ollama github.com/ollama/ollama gitleaks, secret scanning @gitleaks github.com/gitleaks/gitleaks Luddite Scout, static pre-flight github.com/TechLuddite/Luddi… PostgreSQL, Gitea's database github.com/postgres/postgres Traefik, TLS and routing @traefik github.com/traefik/traefik Docker, which runs every service @docker github.com/moby/moby Omarchy, the desktop the whole lab runs on @omarchy github.com/omacom/omarchy Full pipeline, topology and a comparison with GitHub + Copilot, CodeRabbit and GitLab Duo in the image. Also, one special shout-out, to @MichaelGannotti because...infographics! :D
6
2
2
16
1,012
🚀 A new chapter for the Gitea CLI starts today: gt 1.0.0 is here! The first stable release of gt, the official Gitea CLI. With it, gt replaces tea: tea gets no further releases and its repository is archived. ⬆️ gt upgrade updates gt itself, and gt tells you when a new release is out 🧩 Extensions: install gt-NAME from any Gitea instance, GitHub CLI extensions included 🍒 gt pr backport cherry-picks merged pull requests onto release branches 🗂️ New gt project and gt runner commands 🤖 In Gitea Actions, GITEA_TOKEN is all you need 📊 --csv next to --json and --jq ℹ️ From 1.0 on, gt follows semantic versioning: commands, flags, --json fields and exit codes stay stable within 1.x. Requires Gitea 28+. ⚠️ Still on tea? Now is the time to move. The migration guide maps tea's commands to gt's: gitea.com/gitea/cli/src/bran… Read more in our blog post: blog.gitea.com/release-of-gi…
2
18
2
151
9,232
✨The TeaGo app now includes widget support. If you rely on @giteaio as a local git server, TeaGo is well worth exploring.
2
1
2
194
🚀 Gitea 28.2.0 is here! This release includes important security fixes, along with improvements to Gitea Actions, pull requests, authentication, and package management. 🔒 Security fixes 🛠️ Bug fixes across the platform 📦 39 merged PRs from our community We strongly recommend upgrading! 👉 blog.gitea.com/release-of-28… #Gitea #OpenSource #DevOps
10
1
64
2,300
Gitea Runner 5.0.0 is here! 🚀 This release makes builtin:checkout a full replacement for actions/checkout, plus more improvements to Gitea Actions: ✅ builtin:checkout now supports SSH keys, LFS, submodules, sparse checkout & partial clones ⚡ Actions are now downloaded with the Git CLI, which is faster and supports SHA-256 repos ☸️ Kubernetes backend (since 4.1.0) runs each job as a pod, no Docker daemon needed 🔐 Mutual TLS & extra headers for reverse proxies 🧩 ${NAME} env var expansion in config, plus read-only :ro volumes 📊 New gitea_runner_state metric, and metrics now follow the OpenTelemetry conventions ⚠️ There are a few breaking changes: Git 2.34.1+ is required, jobs must set runs-on, and literal ${…} in config must be escaped as $${…}. Check the upgrade notes before you update. Upgrade your runners and check out the full release notes: blog.gitea.com/release-of-ru…
2
19
1
139
5,583
Gitea 28.1.0 is out! 🚀 This is the first maintenance release for the 28 series, including important security fixes and fixes for regressions reported after 28.0.0. Highlights: • Security fixes • Protected branch pushes from Actions restored • npm registry fixes and improved compatibility • MySQL, MariaDB & MSSQL transaction fixes • 38 merged PRs from the community We strongly recommend upgrading as soon as possible. blog.gitea.com/release-of-28… #Gitea #OpenSource #DevOps #Git
10
83
3,952
Gitea 28.0.0 is here! 🚀 Starting with this release, we’re dropping the historical “1.” prefix — welcome to Gitea 28! Highlights: 🔐 Audit logging 🤖 Dedicated bot accounts 🔑 HTTPS deploy tokens 👥 Code owner approval rules 🔍 PR diff search & filters ⚡ Actions queue view & artifact previews 🛠️ And much more A huge thank you to everyone who contributed to this release! ❤️ Read the full release notes: blog.gitea.com/release-of-28… #Gitea #OpenSource #DevOps #Git
7
34
4
264
17,386
Gitea Runner 4.0.0 is here! 🚀 Highlights: ⚡ Built-in actions, starting with builtin:checkout 🗄️ Shared S3-compatible cache 🔭 OpenTelemetry tracing 🔗 self: action references 🐳 Improved container & cache handling And much more. Check out the full release: blog.gitea.com/release-of-ru… #Gitea #DevOps #CI #OpenSource
7
26
4
227
14,760
Gitea 1.27.3 is now available! This third patch release for the 1.27 series includes important security fixes across Gitea Actions, the API, package registry, and repository migration, plus bug fixes for Actions, packages, and the UI. We strongly recommend upgrading as soon as possible. blog.gitea.com/release-of-1.… #gitea #opensource #devops #git
12
95
6,138
🚀 Gitea for VS Code 1.0.0 is here! - Gitea Actions, pull requests, and repository settings now live in the editor: workflow runs and job logs, native diffs and reviews, artifacts, secrets, and variables, without switching to the browser for every check. - Work with multiple Gitea instances - Works with VS Code, Cursor, VSCodium, and Windsurf. Less context switching. More building. blog.gitea.com/release-of-gi… #Gitea #VSCode #OpenSource #DevTools
2
16
83
5,044
Gitea 1.27.2 is now available. 📷 This release includes a large batch of security fixes — covering markup rendering, external renderers, API token scopes, two-factor authentication, repository permissions and Gitea Actions — alongside bug fixes for Actions, packages, LFS, storage and the UI. We strongly recommend upgrading as soon as possible. Read the release notes: blog.gitea.com/release-of-1.…
7
29
2,823
Gitea Runner 3.0.0 is here! 🚀 This release brings major improvements to Gitea Actions: ✅ Stock actions/upload-artifact, actions/download-artifact & actions/cache — no fork required 🔐 Stronger container isolation & encoded-secret masking 🪝 Job lifecycle hooks 🌐 Better proxy support 🛠️ Tool cache & mount improvements Upgrade your runners and check out the full release notes: blog.gitea.com/release-of-ru… #Gitea #DevOps #CICD #OpenSource
5
6
52
4,020
Gitea 1.27.1 is now available. This release includes important security fixes and a large batch of bug fixes, with significant improvements to Gitea Actions, repository workflows, authentication, pull requests, and more. We strongly recommend upgrading as soon as possible. Read the release notes: blog.gitea.com/release-of-1.… #Gitea #OpenSource #DevOps #Git
5
11
1
30
4,417
Gitea 1.27.0 is out. Highlights: reusable workflows as first-class jobs, job summaries, smarter cancellation with Runner 2.0.0, Jupyter Notebook rendering, multiple projects per issue, OpenAPI 3.0, and important security fixes. Upgrade now: blog.gitea.com/release-of-1.… #git #gitea #opensource #devops
3
7
1
39
2,587
Gitea 1.26.3 and 1.26.4 are now available. 1.26.3 includes a broad set of security fixes, along with important bug fixes and stability improvements. 1.26.4 follows immediately to address a repository code-page regression introduced in 1.26.3, plus one additional security fix. We recommend upgrading. blog.gitea.com/release-of-1.… #gitea #git #devops #opensource
4
1
31
2,770
Day 23 of 100 Days of DevOps - KodeKloud! Task: Fork a Git Repository on Gitea. →Forking creates your own copy of someone else's repo so you can work on it independently. #DevOps #100DaysOfDevOps #AbdisamadYusuf @KodeKloudHQ @giteaio
1
2
355