For a FAQ on how Forgejo and Gitea are related, see the dedicated comparison page.
Forgejo (pronounced /forˈd͡ʒe.jo/) is inspired by forĝejo, the Esperanto word for forge.
The vast majority of Forgejo’s users are developers of free and open source software.
Forgejo maintains a list of public instances.
Forgejo’s governance is collectively defined by its contributors.
For less urgent conversations and real-time discussions, there is a Matrix Space that is open to everyone.
The Forgejo domains are in the custody of the non-profit Codeberg e.V..
At this point in time, Forgejo has not registered any trademarks.
Codeberg is a non-profit association registered in Berlin, Germany. The abbreviation e.V. stands for eingetragener Verein, which translates as ‘registered association’.
As defined by its Bylaws, its goal is to “guarantee the openness and continued availability of free software”.
Forgejo has to abide by Codeberg’s goals. We believe that this arrangement reinforces the longevity of Forgejo, as far as the project’s stability and financial security is concerned.
For more information, see Codeberg’s Documentation.
For the time being, yes. Up until early 2024, Forgejo used to include all of Gitea. All commits made on Gitea were also present in Forgejo, and upgrading from Gitea to Forgejo was as easy as changing the URL from which you get your releases from.
Upgrading from the latest Gitea version released before the hard fork (v1.21.5) is still guaranteed to work. Upgrading from releases made after that, aren’t. It may remain possible, but as the two projects naturally drift apart, migration will become more risky.
Yes. The Code of Conduct applies to all spaces that the Forgejo project is responsible for.
Sustaining Free Software projects developed in the interest of the general public is an ongoing challenge.
Forgejo relies on a mixture of volunteer contributions, grants, donations and employee delegation to keep going.
- Codeberg e.V. owns Forgejo’s domains, provides resources and cooperates closely with Forgejo.
- Forgejo’s governance structures remain independent of Codeberg’s.
- Forgejo applies for grants to meet its goals more efficiently.
- Contributors can independently accept employment contracts.
More details are available on Forgejo’s repository dedicated to sustainability.
Apart from that, there are various contributors spend a lot of their time issuing improvements based on user feedback. Forgejo has a user research project with the goal of building a more concrete roadmap. If you are interested in participating, please join the chat room.
Security issues are managed by a team sharing the effort between Codeberg and Forgejo.
The security team is available at
firstname.lastname@example.org (GPG public key 1B638BDF10969D627926B8D9F585D0F99E1FB56F) and is tasked to identify, define, and respond to vulnerabilities.
In order to prevent a takeover from a for-profit company, it was suggested to change the license to AGPL. However, no agreement was reached. Instead, Forgejo agreed to allow contributions compatible with GNU General Public License v3.0 or later. As of January 2024, such a contribution has not been made yet.
The 1.19 tag is set to be the latest patch release, starting with 1.19.0-2. 1.19 will then be equal to 1.19.1-0 when it is released and so on. It can conveniently be used for automated upgrades to the latest stable release.
Because upgrading from 1.X to 1.X+1 (for instance from 1.18 to 1.19) requires a manual operation and human verification. However it is possible to use the X.Y tag (for instance 1.19) to get the latest point release automatically.
Forgejo introduces two new themes: light version named forgejo-light and a dark version named forgejo-dark. They are the default for a new installation but will need to be set explicitly if the
app.ini file already has a custom list of themes. For instance, if it looks like this:
THEMES = gitea-auto,gitea-light,gitea-dark
the forgejo-auto, forgejo-light and forgejo-dark can be added as follows:
THEMES = forgejo-auto,forgejo-light,forgejo-dark,gitea-auto,gitea-light,gitea-dark
Although the Forgejo codebase is known to be easy to built for Windows and reliably run with a mssql database, there currently is no expertise on either of those in the Forgejo community. Maintaining a distribution targetting a given database and Operating System requires someone to build and maintain the release pipeline, figure out the root cause of bugs and fix them.