Beyond coding. We forge.
Find a file
Earl Warren 39de9bda2a
[BRANDING] Add Forgejo light, dark, and auto themes: fix import
Closes: https://codeberg.org/forgejo/forgejo/issues/562
(cherry picked from commit 2b0dc1f80f)
(cherry picked from commit 690dde103f)
(cherry picked from commit 1443ea4620)
2023-04-12 01:22:28 +02:00
.gitea [WORKFLOW] issues & pr templates 2023-04-11 23:49:18 +02:00
.woodpecker [BRANDING] parse FORGEJO__* in the container environment 2023-04-12 01:18:29 +02:00
assets [BRANDING] add Forgejo logo 2023-04-12 01:18:28 +02:00
build Consume hcaptcha and pwn deps (#22610) 2023-01-29 09:49:51 -06:00
cmd [BRANDING] Rebrand dump log 2023-04-12 01:22:28 +02:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-04-12 01:18:29 +02:00
CONTRIBUTING [DOCS] CONTRIBUTING 2023-04-11 23:49:18 +02:00
custom/conf [BRANDING] DEFAULT_ACTIONS_URL = https://codeberg.org 2023-04-12 01:22:27 +02:00
docker [BRANDING] container images: set APP_NAME 2023-04-12 01:18:28 +02:00
docs Update documentation to explain which projects allow Gitea to host static pages (#23993) (#24058) 2023-04-11 18:43:35 +02:00
models [BRANDING] reserve forgejo-actions username 2023-04-12 01:22:27 +02:00
modules [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-04-12 01:22:28 +02:00
options Title can be empty when creating tag only (#23917) (#23961) 2023-04-07 20:13:57 +08:00
public [BRANDING] Custom loading animation for Forgejo 2023-04-12 01:18:28 +02:00
releases [DOCS] RELEASE-NOTES: 1.19.0 2023-04-11 23:49:19 +02:00
routers [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-04-12 01:22:28 +02:00
services [BRANDING] define the forgejo webhook type 2023-04-12 01:18:29 +02:00
snap
templates [BRANDING] link to forgejo.org/docs instead of docs.gitea.io 2023-04-12 01:22:28 +02:00
tests [BRANDING] Update nodeinfo branding 2023-04-12 01:22:21 +02:00
tools Move fuzz tests into tests/fuzz (#22376) 2023-01-09 15:30:14 +08:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes: fix import 2023-04-12 01:22:28 +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 test_env: hardcode major go version in use (#23464) 2023-03-14 04:12:14 -04:00
.editorconfig
.eslintrc.yaml Refactor hiding-methods, remove jQuery show/hide, remove .hide class, remove inline style=display:none (#22950) 2023-02-19 12:06:14 +08:00
.gitattributes
.gitignore [CI] implementation: Woodpecker based CI 2023-04-11 23:03:51 +02:00
.gitpod.yml Split default gitpod view to include all tasks (#22555) 2023-01-20 13:46:33 -06:00
.golangci.yml Fix .golangci.yml (#22868) 2023-02-11 21:44:53 +00:00
.ignore
.lgtm
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml Replace Less with CSS (#23508) 2023-03-16 21:04:39 -04:00
BSDmakefile
build.go User/Org Feed render description as per web (#23887) (#23906) 2023-04-04 00:44:50 -04:00
CHANGELOG.md Add CHANGELOG for 1.19.0 (#23583) (#23586) 2023-03-20 16:34:28 +08:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-04-11 23:49:18 +02:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [BRANDING] symlink gitea to forgejo in docker containers 2023-04-12 01:22:27 +02:00
Dockerfile.rootless [BRANDING] symlink gitea to forgejo in docker containers 2023-04-12 01:22:27 +02:00
go.mod Do not crash when parsing an invalid workflow file (#23972) (#23976) 2023-04-07 09:55:59 -04:00
go.sum Do not crash when parsing an invalid workflow file (#23972) (#23976) 2023-04-07 09:55:59 -04:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-04-11 23:49:18 +02:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-04-12 01:22:27 +02:00
MAINTAINERS Add sillyguodong to maintainers (#23067) 2023-02-22 18:32:00 +08:00
Makefile [BRANDING] Replace branding in Swagger 2023-04-12 01:18:29 +02:00
package-lock.json Polyfill the window.customElements (#23592) (#23595) 2023-03-20 19:52:05 +01:00
package.json Polyfill the window.customElements (#23592) (#23595) 2023-03-20 19:52:05 +01:00
playwright.config.js
README.md [BRANDING] add Forgejo logo 2023-04-12 01:18:28 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES: 1.19.0 2023-04-11 23:49:19 +02:00
vitest.config.js Update JS dependencies and eslint (#22190) 2022-12-20 17:15:47 -05:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-04-11 23:49:18 +02:00

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.