HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
go-gitea
gitea
Go2016–2026
go-gitea / gitea

gitea

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

132Distinct people
161Mentions
2Explicit recommenders
59KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

  • OpenSUSE/SUSE — OpenSUSE/SUSE uses Gitea at src.opensuse.org as part of their development workflows. They also contribute back to Gitea via pull requests. Source

What people are saying

I use Gitea and I love it. The network effects and reach of GH are holding people back from discovering / using / contributing to other forges (gitlab, gitea, sourcehut) that…

rapnie used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:59:04 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year161 dated mentions

Observed mentions: 2016-12-27 18:04:28 UTC to 2026-10-01 08:37:06 UTC.

0102030402016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 26 mentions; 4 submissions, 22 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 17 mentions; 3 submissions, 14 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 38 mentions; 3 submissions, 35 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 23 mentions; 2 submissions, 21 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC1019
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC26422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC615
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC11110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC17314
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC38335
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC23221
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC12111
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC10010
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC716

What Hacker News says

12 sources
re my commentary nine months ago: I thought Gitea was fairly safe, as they were not requiring a CLA. (https://news.ycombinator.com/item?id=39680587) They still seem to only require a DCO, so I don't think they're gearing up for a commercialization rugpull... yet? Some of the forgejo devs apparently believe that a collective copyright header is the same thing as a copyright assignment: https://github.com/go-gitea/gitea/pull/27455 & https://codeberg.org/forgejo/discussions/issues/67 I disagree on that point personally, but is there precedent here anywhere in the world? Now that forgejo is not hard-tracking the gitea source, maybe we'll see in a year or two which project has better technical velocity or whatnot. IMO it's a coin toss between the two at this juncture.
In Gitea 1.22 is the last version to allow a transparent ugprade to Forgejo
See this issue: https://github.com/go-gitea/gitea/issues/1029 For years, "self-hosting" Gitea wasn't done because it was missing a bunch of useful collaboration features. Now, it looks like that gap has been closed. All of the specific features mentioned in that issue seem to have been fixed, and the big remaining task is figuring out below to actually migrate all the existing data out of GitHub -- which doesn't seem to be super high on the priority list.
In Gitlab names Bill Staples as new CEO
We're not, and they're still in the process of discussion. It seems a bit early to fork and witch-hunt [0]: > So clarification here: you asked me about that, but I haven’t been able to respond to you due to my illnesses and I’m just getting back on my feet now. So it’s not that it hasn’t been well received, it’s that I’ve been physically unable to respond to you. [0]: https://github.com/go-gitea/gitea/pull/24257#issuecomment-23...
In Gitea blocks PR from community, charging $$ for open-source contributions
Very cool! I am also a big fan of jq. And I think using DuckDB and SQL probably makes a lot of sense in a lot of cases. But I think the examples are very geared towards being better solved in SQL. The ideal jq examples are combinations of filter (select), map (map) and concat (.[]). For example, finding the right download link: $ curl -s https://api.github.com/repos/go-gitea/gitea/releases/latest \ | jq -r '.assets[] | .browser_download_url | select(endswith("linux-amd64"))' https://github.com/go-gitea/gitea/releases/download/v1.15.7/gitea-1.15.7-linux-amd64 Or extracting the KUBE_CONFIG of a DigitalOcean Kubernetes cluster from Terraform state: $ jq -r '.resources[] | select(.type == "digitalocean_kubernetes_cluster") | .instances[].attributes.kube_config[].raw_config' \ ter
Read the rest
raform.tfstate apiVersion: v1 kind: Config clusters: - cluster: certificate-authority-data: ... server: https://...k8s.ondigitalocean.com ...
In DuckDB as the New jq
Same [1]. Zoom being outsourced to the implementing platform is one major pain-point. That example from us has grown in size. Having to bump the processing limit multiple times for mermaid to not refuse processing big diagrams, using touch zoom gestures on the laptop, because the diagram is so small, that browser zoom can't provide enough magnification, the list goes on. We are clearly using the wrong tool for a diagram of this complexity, but the practicality of seeing commit changes in the diff, what property was changed by whom and instantly having the visual feedback in the Pull Request is just way too useful to switch to a "proper" tool. [1] https://github.com/go-gitea/gitea/issues/25803
In Mermaid Chart, a Markdown-like tool for creating diagrams, raises $7.5M
It's a tangent, but I think it's interesting that Gitea started trying to self host in Feb 2017 (https://github.com/go-gitea/gitea/issues/1029) and hasn't got there yet (based on how active the github issues/PR page are). https://about.gitea.com/ offers me a "free cloud trial" and otherwise sounds very like other web front ends to git. So like github, except they don't trust it themselves. In contract forgejo has "Self-hosted alternative to GitHub" written in big letters on the landing page. https://codeberg.org/forgejo is indeed self hosted.
In Forgejo makes a full break from Gitea
I haven't seen someone mentioning Go's issues with crypto yet. After OpenSSH deprecated SHA1, the Go team took a year (!) to add support for SHA2 to x/crypto/ssh [1]. Gitea was one famous victim [2]. Furthermore it doesn't instill confidence to see a crypto maintainer bashing on GnuPG [3] and trying to discredit Dan Bernstein [4]. [1]: https://github.com/golang/go/issues/49269 [2]: https://github.com/go-gitea/gitea/issues/17798 [3]: https://twitter.com/FiloSottile/status/1127643698676797441 [4]: https://twitter.com/FiloSottile/status/1555669786826244096
In Go: What we got right, what we got wrong

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.