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, 4:43:50 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

38 sources
Gogs is a clone of GitHub and GitLab (which were both originally written in Ruby with the Ruby on Rails CoC Convention-over-Configuration Web Framework), which were built because Trac didn't support Git or multiple projects, Sourceforge didn't support Git or on-prem, and git patchbombs as attachments over emailing lists needed Pull Requests, and Issues and PRs should pull from the same sequence of autoincrement (*) integer keys. - You can do ~GitHub Pages with Gitea and an idempotent git post-receive-hook that builds static HTML from a repo revision, tests, deploys to revid/ and updates a latest/ symlimk, and logs; or with HTTP webhooks. - "Feature: Allow interacting with tickets via email" https://github.com/go-gitea/gitea/issues/2386#issuecomment-6... - It's not safe to host Gitea on the same server as the CI (e.g. DroneCI) host if you
Read the rest
grant permissions to the docker socket to the CI container: you need another VM at least to run the CI controller and workers on_push() with Gitea. https://docs.drone.io/server/provider/gitea/ : > Please note we strongly recommend installing Drone on a dedicated instance. We do not recommend installing Drone and Gitea on the same machine due to network complications, and we definitely do not recommend installing Drone and Gitea on the same machine using docker-compose. GitHub and GitLab centralize git for project-based collaboration, which is itself a distributed system.
In A Message from Lunny on Gitea Ltd. and the Gitea Project
>Throughout the life of the project, I have always personally owned both domains. As it continued to grow, I additionally trademarked the name “Gitea” in order to protect the project’s brand. (More on the trademark later.) The issue as I read it is that he communicated to the community that he isn't the BDFL (benevolent dictator for life) of the project but rather that there is democratic ownership. >https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#... Clearly that's not the case. Communities can be mostly fine with a BDFL system if it's made clear however they tend to be less fine with feeling like they've been lied to.
In A Message from Lunny on Gitea Ltd. and the Gitea Project
https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#... The current holder of the domains and trademarks was elected as the custodian for a limited time (through the end of 2022). The terms of that election included an agreement to hand over custody to their eventual elected successor. But they've instead created this for-profit company and transferred it ownership of the assets. What happens when a new custodian is elected by the community who is not affiliated with this new company? Will the company give up control of the assets as previously agreed?
In Open letter to Gitea
There only are three demands: > A non-profit organisation owned by the Gitea community is created. > The Gitea trademark and domains are transferred to the non-profit. > The name of the company is changed to avoid any confusion with the non-profit. A week ago the Gitea project was an informal community trusting elected individuals with essential assets such as the domains and the trademark. They had a clear moral bound (see https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#...) to pass on the ownership of the project to their successor. But they thought it was ok to create a company and take the domains and trademark as if they were their property. Maybe the absence of a legal bound made them forget their promise, their moral obligation towards the Gitea community. Creating a non-profit will avoid that kind of problem in the fut
Read the rest
ure and give back the domains and the trademark to the Gitea community. If the president of a non-profit was to transfer the domain name to a for-profit company they exclusively control, the members of the non profit will be in a position to sue the president for embezzlement. If the for profit company refuses to give back the domains and trademark, that would be very damaging to the project. The post from Harald Welte on that topic in the Gitea forum is enlightening in that regard, see https://discourse.gitea.io/t/open-source-sustainment-and-the... The other points you cite from the Open Letter are merely suggestions for future improvements (as stated in the letter), not demands.
In Open letter to Gitea
As I've mentioned elsewhere in this thread, I'm a contributor to gitea and have no ownership in the new organization. I genuinely would like some clarification to the points in the letter, as I'm trying to advise the owners and understand my future with the project. It seems like the demands are: > Implementing an intuitive and fair election process. I think we do that now: https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#... Anyone who has contributed to the gitea project more than 2x PRs is invited to be a maintainer. Every maintainer gets 3 votes. Maybe there are some suggestions for improving - please open a PR. > Describing the ways in which democratic decisions are to be made. Again, I'm just confused what's being requested. Moving on. > Providing accessible places where all relevant information can be found. This seems l
Read the rest
ike the same request as above. Or maybe a request for better documentation. I agree. Open a PR, don't fork gitea. > Establishing a DoOcracy that works and continue to improve it. I agree with this and I suspect that was the intention with the original reference to DAOs, but needs to be clarified. > A non-profit organisation owned by the Gitea community is created. > The Gitea trademark and domains are transferred to the non-profit. > The name of the company is changed to avoid any confusion with the non-profit. Does anyone have experience with how this is typically handled? It seems like this is the only actionable request. What are some examples of non-profit open-source companies? Is that typical?
In Open letter to Gitea
Gitea contributor ("maintainer") here [0] - we were blindsided by the original Gitea Ltd. announcement too, but if you look at any of answers in discord regarding clarification, it's pretty clear that this is a better situation than the gitea assets being owned by a single person, and the intention is NOT to syphon money from the project or start a shillcoin or something like that. The general consensus from us maintainers on the "Open Letter" is that it's an overreaction. It's not supported by a vast majority of the maintainers of the project and spearheaded by folks who have contributed very little. A VAST majority of folks contributing to gitea are still onboard. We need answers. The communication was poorly handled. The original announcement was completely bereft of details and now we finally have a draft of updated clarifications tha
Read the rest
t should be posted soon (thankfully, this time we're being consulted for feedback). I think the original intention was "we're seeing some revenue coming in and now we're workshopping ways to get those funds back to contributors and maintain the project in a sustainable way", but a lot of poorly-chosen words were used, and panic ensued. TL;DR: give us some time to set it all straight and if it really looks like incentives are misaligned, please provide some constructive criticism. ALSO, WE WOULD LOVE HELP & FEEDBACK FROM FOLKS WHO HAVE MAINTAINED SIMILAR PROJECTS SUCCESSFULLY [0] https://github.com/go-gitea/gitea/graphs/contributors
In Open letter to Gitea
A bit of context (why this matters) is useful: https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#... > Since Gitea is a pure community organization without any company support, to keep the development healthy we will elect three owners every year. > When the new owners have been elected, the old owners will give up ownership to the newly elected owners According to CONTRIBUTING.md, this dates back to 2016. The new company represents a shift from the community model that attracted many developers and users. The issue is that ultimately Lunny holds the trademark and isn't legally bound to uphold whatever agreement is stated in the repo.
In Open letter to Gitea
>even the gitea people are using github for development. The reason they mention on the migration issue is, that not all features needed are ready. They e.g. implemented issue deletation a few months ago. Actually,data gravity is the issue, not features. https://github.com/go-gitea/gitea/pull/18165 needs to be merged to be able to leave Github.
In GitLab 15.5

Showing the 15 most recent of 38 sources. Enable JavaScript to search and browse every indexed mention.

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.