Go to file
Earl Warren f5dbac2d6a
[BRANDING] link to forgejo.org/docs instead of docs.gitea.io
Fix the link that was 404.

(cherry picked from commit ae515d7258)
(cherry picked from commit facc2367f0)
2023-03-20 12:04:18 +01:00
.gitea
.woodpecker [BRANDING] parse FORGEJO__* in the container environment 2023-03-18 18:19:03 +01:00
CONTRIBUTING
assets
build
cmd [BRANDING] Rebrand dump log 2023-03-18 18:19:05 +01:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-03-18 18:19:03 +01:00
custom/conf Add `.patch` to `attachment.ALLOWED_TYPES` (#23580) (#23582) 2023-03-20 11:08:32 +01:00
docker
docs Add `.patch` to `attachment.ALLOWED_TYPES` (#23580) (#23582) 2023-03-20 11:08:32 +01:00
models [BRANDING] reserve forgejo-actions username 2023-03-18 18:19:04 +01:00
modules Add `.patch` to `attachment.ALLOWED_TYPES` (#23580) (#23582) 2023-03-20 11:08:32 +01:00
options
public
releases
routers Match api migration behavior to web behavior (#23552) (#23573) 2023-03-19 09:21:17 +01:00
services Merge remote-tracking branch 'forgejo/v1.19/forgejo-privacy' into v1.19/forgejo 2023-03-18 20:05:28 +01:00
snap
templates [BRANDING] link to forgejo.org/docs instead of docs.gitea.io 2023-03-20 12:04:18 +01:00
tests [BRANDING] Update nodeinfo branding 2023-03-18 18:19:04 +01:00
tools
web_src [BRANDING] Add Forgejo light, dark, and auto themes: fix import 2023-03-20 11:30:24 +01:00
.air.toml
.changelog.yml
.dockerignore
.drone.yml
.editorconfig
.eslintrc.yaml
.gitattributes
.gitignore
.gitpod.yml
.golangci.yml
.ignore
.lgtm
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
BSDmakefile
CHANGELOG.md Add CHANGELOG for 1.19.0 (#23583) (#23586) 2023-03-20 11:08:33 +01:00
CONTRIBUTING.md
DCO
Dockerfile [BRANDING] symlink gitea to forgejo in docker containers 2023-03-18 18:19:04 +01:00
Dockerfile.rootless [BRANDING] symlink gitea to forgejo in docker containers 2023-03-18 18:19:04 +01:00
LICENSE
MAINTAINERS
Makefile Merge remote-tracking branch 'forgejo/v1.19/forgejo-i18n' into v1.19/forgejo 2023-03-18 20:05:33 +01:00
README.md
RELEASE-NOTES.md
build.go
go.mod
go.sum
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-03-18 18:19:05 +01:00
package-lock.json
package.json
playwright.config.js
vitest.config.js
webpack.config.js

README.md

Welcome to Forgejo

Hi there! Tired of big platforms playing monopoly? Providing Git hosting for your project, friends, company or community? Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo the Esperanto word for forge) has you covered with its intuitive interface, light and easy hosting and a lot of builtin functionality.

Forgejo was created in 2022 because we think that the project should be owned by an independent community. If you second that, then Forgejo is for you! Our promise: Independent Free/Libre Software forever!

What does Forgejo offer?

If you like any of the following, Forgejo is literally meant for you:

  • Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!
  • Project management: Besides Git hosting, Forgejo offers issues, pull requests, wikis, kanban boards and much more to coordinate with your team.
  • Publishing: Have something to share? Use releases to host your software for download, or use the package registry to publish it for docker, npm and many other package managers.
  • Customizable: Want to change your look? Change some settings? There are many config switches to make Forgejo work exactly like you want.
  • Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more. If you have advanced needs, Forgejo has you covered.
  • Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
  • Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub, and create a collaborative network of personal instances. Interested? Read more

Learn more

Subscribe to releases and blog post on our website, find us on the Fediverse or hop into our Matrix room if you have any questions or want to get involved.

Get involved

If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.