Discofork
Repository brief

go-gitea/gitea

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:53:22.689Z
3mo ago

go-gitea/gitea

Gitea is a large, active self-hosted Git service project: "Git with a cup of tea!" It targets an all-in-one development platform with Git hosting, code review, team collaboration, package registry, and CI/CD. The repo is well-maintained, very popular, and clearly suitable for forks that want an established upstream with ongoing change.

GitHub
Loading tags...
Stars54,593
Forks6,509
Default branchmain
Last pushed2026-03-30T00:29:46Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if the local customizations are worth the maintenance cost. For most adopters, current upstream Gitea is the safer default; this fork fits teams that value downstream control over staying current.

Prefer this fork if you want Gitea with Blender-specific customization and can live with divergence from upstream. Prefer upstream if you want the broadest compatibility, easiest upgrades, and fewer local patches to carry.

Choose this fork only if you want the Codeberg-aligned downstream and can accept a stale, significantly diverged codebase. For most adopters who want current features, fixes, and lower maintenance risk, upstream Gitea is the safer default.

Choose this fork only if you specifically want an old, lightly customized Gitea snapshot. For most adopters, upstream Gitea is the better fit because this fork is stale, far behind, and likely expensive to maintain.

Prefer upstream Gitea unless you specifically need this 2020-era fork for compatibility or an already-deployed custom baseline. This fork looks stale and materially behind, so it is a poor choice for new adopters who want current functionality and maintenance.

Prefer this fork only if you need its existing customizations and are willing to own a stale, highly divergent codebase. If you want current Gitea behavior, security fixes, and easier upgrades, upstream is the safer choice.

Choose this fork only if you need its custom build and asset stack enough to accept a substantial merge burden. If you want a low-friction Gitea install with current upstream behavior and supportability, upstream is the safer default.

Prefer this fork if you want a customized Gitea deployment and can own ongoing divergence. Prefer upstream if you want current fixes, lower upgrade risk, and less maintenance overhead.

Prefer this fork if git-annex support is a core requirement. Prefer upstream Gitea if you want the broadest feature set, the fastest bug-fix stream, and easier maintenance.

Prefer this fork only if you need its old 2020 baseline or its specific local tweaks. For most adopters, upstream Gitea is the better choice because this fork is stale and materially behind.

go-gitea/gitea · Discofork