Go to file
Gusted a4a5fdbde4
[BRANDING] Replace branding in Swagger
- "Gitea" is automatically being determined in Swagger and cannot be
overridden, therefor we override it after `swagger generate spec` is run.
- Resolves https://codeberg.org/forgejo/forgejo/issues/226

(cherry picked from commit 0b45380765)

[BRANDING] Change Swagger title to Forgejo API

(cherry picked from commit 79f6a70b53)
(cherry picked from commit 6cd47afe33)
(cherry picked from commit a7ae2e4c09)
(cherry picked from commit 59f837e466)
(cherry picked from commit c1c3d1f0e6)
(cherry picked from commit 4b088713fb)
(cherry picked from commit 3df1d21371)
2023-04-03 11:40:26 +02:00
.gitea [WORKFLOW] issues & pr templates 2023-04-03 10:34:06 +02:00
.woodpecker [CI] implementation: Woodpecker based CI 2023-04-03 09:49:59 +02:00
CONTRIBUTING [DOCS] CONTRIBUTING 2023-04-03 10:34:05 +02:00
assets [BRANDING] add Forgejo logo 2023-04-03 11:32:48 +02:00
build Try to catch more broken translations (#23867) 2023-04-03 11:12:47 +08:00
cmd [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-04-03 11:40:26 +02:00
contrib [BRANDING] Rebrand systemd service (#137) 2023-04-03 11:32:48 +02:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2023-04-03 11:32:48 +02:00
docker [BRANDING] container images: set APP_NAME 2023-04-03 11:40:26 +02:00
docs Rename actions unit to `repo.actions` and add docs for it (#23733) 2023-04-03 00:05:37 -04:00
models Rename actions unit to `repo.actions` and add docs for it (#23733) 2023-04-03 00:05:37 -04:00
modules [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-04-03 11:40:26 +02:00
options Rename actions unit to `repo.actions` and add docs for it (#23733) 2023-04-03 00:05:37 -04:00
public [BRANDING] Custom loading animation for Forgejo 2023-04-03 11:40:14 +02:00
releases [DOCS] RELEASE-NOTES.md 2023-04-03 10:34:06 +02:00
routers [BRANDING] Rebrand default config settings for new installs (#140) 2023-04-03 11:32:48 +02:00
services Check `IsActionsToken` for LFS authentication (#23841) 2023-04-02 22:43:11 +08:00
snap Remove unnecessary whitespace in snapcraft.yaml (#22090) 2022-12-10 08:31:16 -06:00
templates [BRANDING] Replace branding in Swagger 2023-04-03 11:40:26 +02:00
tests [ACTIONS] forgejo actions --registration-token-admin 2023-04-03 10:43:02 +02:00
web_src [BRANDING] [v1.20] Add Forgejo light, dark, and auto themes 2023-04-03 11:40:26 +02:00
.air.toml Add more test directory to exclude dir of air, remove watching templates from air include dir because gitea has internal mechanism (#22246) 2022-12-27 14:00:34 +08:00
.changelog.yml
.dockerignore
.drone.yml Update JS deps (#23853) 2023-04-02 19:47:14 -04:00
.editorconfig
.eslintrc.yaml Remove jQuery ready usage (#23858) 2023-04-01 18:40:22 -04:00
.gitattributes
.gitignore [CI] implementation: Woodpecker based CI 2023-04-03 09:49:59 +02:00
.gitpod.yml Add `deps-docs` command to makefile (#23686) 2023-03-24 14:42:31 -04:00
.golangci.yml Fix .golangci.yml (#22868) 2023-02-11 21:44:53 +00:00
.ignore
.lgtm
.markdownlint.yaml
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml
.stylelintrc.yaml Update JS deps (#23853) 2023-04-02 19:47:14 -04:00
BSDmakefile
CHANGELOG.md Add CHANGELOG for 1.19.0 (#23583) 2023-03-20 15:42:23 +08:00
CODE_OF_CONDUCT.md Add Gitea Community Code of Conduct (#23188) 2023-03-09 10:49:34 +08:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-04-03 10:34:05 +02:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] implementation: forgejo container images 2023-04-03 09:49:59 +02:00
Dockerfile.rootless [CI] implementation: forgejo container images 2023-04-03 09:49:59 +02:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-04-03 10:34:06 +02:00
MAINTAINERS Yarden Shoham has a new email address (#23767) 2023-03-28 18:24:08 +08:00
Makefile [BRANDING] Replace branding in Swagger 2023-04-03 11:40:26 +02:00
README.md [BRANDING] add Forgejo logo 2023-04-03 11:32:48 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-04-03 10:34:06 +02:00
build.go
go.mod Fix checks for `needs` in Actions (#23789) 2023-03-30 22:33:17 +08:00
go.sum Fix checks for `needs` in Actions (#23789) 2023-03-30 22:33:17 +08:00
main.go [ACTIONS] forgejo actions --registration-token-admin 2023-04-03 10:43:02 +02:00
package-lock.json Update JS deps (#23853) 2023-04-02 19:47:14 -04:00
package.json Update JS deps (#23853) 2023-04-02 19:47:14 -04:00
playwright.config.js
vitest.config.js Improve action log display with control chars (#23820) 2023-04-01 20:57:05 +08:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-04-03 10:43:00 +02:00

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.

Learn more

Dive into the documentation, 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.