No description
Find a file
2024-03-21 08:25:40 +01:00
.devcontainer
.forgejo [CI] cascade end-to-end must not try to merge feature branches 2024-02-10 10:53:04 +01:00
.gitea [WORKFLOW] issues & pr templates (squash) fix link to CONTRIBUTING.md 2024-02-05 15:08:04 +01:00
assets Merge branch 'rebase-forgejo-dependency' into wip-forgejo 2024-02-05 18:58:23 +01:00
build [I18n] tooling and process 2024-02-05 15:08:04 +01:00
cmd Merge branch 'rebase-forgejo-dependency' into wip-forgejo 2024-02-05 18:58:23 +01:00
contrib Merge branch 'rebase-forgejo-dependency' into wip-forgejo 2024-02-05 18:58:23 +01:00
custom/conf Merge branch 'rebase-forgejo-dependency' into wip-forgejo 2024-02-05 18:58:23 +01:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2024-02-05 16:02:14 +01:00
docs introduce federated repo 2024-03-21 08:25:40 +01:00
manual-testing@877d11b403 [TESTS] add manual testing instructions as a sub-module 2024-02-08 11:43:43 +01:00
models introduce federated repo 2024-03-21 08:25:40 +01:00
modules Implent checking for list of repos 2024-03-20 16:12:20 +01:00
options Rephrasing for clearness 2024-03-20 16:14:54 +01:00
public [BRANDING] add Forgejo Git Service and migration UI 2024-02-05 16:05:02 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2024-02-05 14:44:32 +01:00
routers Implement single Repo validation and saving POC 2024-03-20 13:21:17 +01:00
services Do not use binding at this stage 2024-03-20 16:13:00 +01:00
snap
templates Remove ToDo 2024-03-20 16:22:35 +01:00
tests Merge remote-tracking branch 'forgejo/forgejo-dependency' into wip-forgejo 2024-02-09 19:00:54 +01:00
web_src Merge branch 'rebase-forgejo-dependency' into wip-forgejo 2024-02-05 18:58:23 +01:00
.air.toml
.changelog.yml Adapt .changelog.yml to new labeling system (#27701) 2023-10-20 00:22:00 +02:00
.deadcode-out result of lint-fix 2024-02-10 15:22:16 +01:00
.dockerignore
.editorconfig
.eslintrc.yaml Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
.gitattributes [META] Use correct language for .tmpl 2024-02-05 14:44:33 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2024-02-05 15:08:04 +01:00
.gitmodules [TESTS] add manual testing instructions as a sub-module 2024-02-08 11:43:43 +01:00
.gitpod.yml
.golangci.yml [GITEA] depguard sha256-simd 2024-02-05 16:54:44 +01:00
.ignore
.markdownlint.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
.npmrc
.spectral.yaml
.stylelintrc.yaml Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
.yamllint.yaml fully replace drone with actions (#27556) 2023-10-11 06:39:32 +00:00
BSDmakefile Fix build errors on BSD (in BSDMakefile) (#27594) 2023-10-13 15:38:27 +00:00
build.go
CHANGELOG.md Fix release link in changelog for v1.21.0 2023-11-14 15:03:49 +01:00
CODEOWNERS [META] Add CODEOWNERS files 2024-02-05 14:44:33 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2024-02-05 14:44:32 +01:00
DCO
Dockerfile [CI] Forgejo Actions based release process 2024-02-05 13:33:59 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2024-02-05 13:33:59 +01:00
go.mod make tidy 2024-02-12 13:07:15 +01:00
go.sum undo rebase conflicts 2024-02-10 15:21:45 +01:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2024-02-05 14:44:32 +01:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2024-02-05 16:05:01 +01:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [BRANDING] add forgejo target to Makefile 2024-02-05 16:05:02 +01:00
package-lock.json Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
package.json Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
playwright.config.js
poetry.lock Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
poetry.toml
pyproject.toml [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2024-02-05 16:02:14 +01:00
README.md [BRANDING] add Forgejo logo 2024-02-05 16:02:13 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md (squash) v1.21.5-0 (squash) go-git 2024-02-05 15:11:35 +01:00
vitest.config.js Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2024-02-05 14:44:32 +01: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.

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.