Beyond coding. We forge. (Code of Conduct: https://codeberg.org/forgejo/code-of-conduct)
Go to file
Loïc Dachary 7e6146c1a8
[BRANDING] reserve forgejo-actions username
(cherry picked from commit 2a25be788b)
(cherry picked from commit b270d5815c)
(cherry picked from commit e7382cc71e)
(cherry picked from commit 665400ea1e)
(cherry picked from commit f5b2c691f1)
(cherry picked from commit 3df97adfef)
(cherry picked from commit 494f6eafc1)
(cherry picked from commit 822e3d2c83)
(cherry picked from commit 7460f12568)
(cherry picked from commit f6cd70881e)
(cherry picked from commit c669ce8173)
(cherry picked from commit 1d5a433e02)
(cherry picked from commit c1a4dc150c)
(cherry picked from commit dd1c971c6c)
(cherry picked from commit 8d2dcd9b1e)
(cherry picked from commit b6bb8fd275)
(cherry picked from commit d4b71fe96e)
(cherry picked from commit e204ec0b23)
(cherry picked from commit 8d9f1174bd)
(cherry picked from commit e314a7d5ba)
(cherry picked from commit 48b3ad5a30)
(cherry picked from commit 71ed4b7c69)
(cherry picked from commit d63324ccb6)
(cherry picked from commit 9249e893db)
(cherry picked from commit 78f156427b)
(cherry picked from commit c3d4a1a602)
(cherry picked from commit 83b1855f55)
(cherry picked from commit 319815d9b1)
(cherry picked from commit c4fcbfd297)
(cherry picked from commit fb58c85222)
(cherry picked from commit 69c24e3e8b)
(cherry picked from commit 1e9ec4737a)
(cherry picked from commit 70439970c1)
2023-10-09 20:59:39 +02:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [CI] Forgejo Actions based release process (squash) use forgejo-curl.sh 2023-10-09 19:30:21 +02:00
.gitea [WORKFLOW] yaml issue templates 2023-10-09 19:11:03 +02:00
.github delete Gitea specific files that need rewriting for Forgejo 2023-10-09 18:46:36 +02:00
assets [BRANDING] add Forgejo logo 2023-10-09 20:51:47 +02:00
build Use Set[Type] instead of map[Type]bool/struct{}. (#26804) 2023-08-30 06:55:25 +00:00
cmd [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-10-09 20:59:38 +02:00
contrib [BRANDING] Rebrand systemd service (#137) 2023-10-09 20:51:47 +02:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2023-10-09 20:51:47 +02:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-10-09 20:59:38 +02:00
docs Add docs section for sub-paths with the container registry (#27505) 2023-10-09 12:45:41 +08:00
models [BRANDING] reserve forgejo-actions username 2023-10-09 20:59:39 +02:00
modules [BRANDING] add the forgejo webhook type & update webhook docs URLs 2023-10-09 20:59:39 +02:00
options [FEAT] add Forgero Git Service 2023-10-09 19:11:03 +02:00
public [BRANDING] Custom loading animation for Forgejo 2023-10-09 20:51:47 +02:00
releases/images [DOCS] RELEASE-NOTES.md 2023-10-09 19:11:01 +02:00
routers [BRANDING] Update nodeinfo branding 2023-10-09 20:59:39 +02:00
services [BRANDING] add the forgejo webhook type & update webhook docs URLs 2023-10-09 20:59:39 +02:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [BRANDING] add the forgejo webhook type & update webhook docs URLs 2023-10-09 20:59:39 +02:00
tests [BRANDING] Update nodeinfo branding 2023-10-09 20:59:39 +02:00
web_src [v1.22] [BRANDING] Add Forgejo light, dark, and auto themes 2023-10-09 20:59:22 +02:00
.air.toml Reduce verbosity of dev commands (#24917) 2023-05-24 20:11:04 +00:00
.changelog.yml Changelog for v1.15.0-rc1 (#16422) 2021-07-15 11:47:57 -04:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.drone.yml Update nodejs installation method in release container (#27207) 2023-09-23 13:18:47 +00:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Update JS and PY dependencies (#27501) 2023-10-08 00:16:20 +00:00
.gitattributes [META] Use correct language for .tmpl 2023-10-09 19:11:02 +02:00
.gitignore [CI] gitignore: emacs backups 2023-10-09 18:25:29 +02:00
.gitpod.yml Add Github related extensions in devcontainer (#25800) 2023-07-14 15:58:02 +08:00
.golangci.yml Use Go 1.21 for golangci-lint (#26786) 2023-08-29 16:25:24 +02:00
.ignore Add /public/assets to .ignore (#26232) 2023-07-30 12:34:20 +02:00
.markdownlint.yaml Enable markdownlint no-duplicate-header (#27500) 2023-10-07 15:30:21 +02:00
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml Add spectral linter for Swagger (#20321) 2022-07-11 18:07:16 -05:00
.stylelintrc.yaml Update JS dependencies (#26025) 2023-07-21 11:34:10 +08:00
.yamllint.yaml Fix more yaml lint errors (#27284) 2023-09-26 12:56:42 -04:00
BSDmakefile update BSDmakefile to latest version from upstream (#24063) 2023-04-11 23:42:22 -04:00
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Add 1.20.5 changelog (#27404) (#27411) 2023-10-03 14:22:03 +00:00
CODEOWNERS [META] Add CODEOWNERS files 2023-10-09 19:11:03 +02:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-10-09 18:46:39 +02:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] Forgejo Actions based release process 2023-10-09 18:25:28 +02:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2023-10-09 18:25:28 +02:00
go.mod Downgrade go-co-op/gocron to v1.31.1 (#27511) 2023-10-07 18:54:02 -04:00
go.sum Downgrade go-co-op/gocron to v1.31.1 (#27511) 2023-10-07 18:54:02 -04:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-10-09 19:11:02 +02:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2023-10-09 19:11:03 +02:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [BRANDING] Replace branding in Swagger 2023-10-09 20:59:38 +02:00
package-lock.json Update JS and PY dependencies (#27501) 2023-10-08 00:16:20 +00:00
package.json Update JS and PY dependencies (#27501) 2023-10-08 00:16:20 +00:00
playwright.config.js Update JS dependencies and eslint config (#21388) 2022-10-10 20:02:20 +08:00
poetry.lock Update JS and PY dependencies (#27501) 2023-10-08 00:16:20 +00:00
poetry.toml Clean up pyproject.toml and package.json, fix poetry options (#25327) 2023-06-18 18:13:08 +00:00
pyproject.toml [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-10-09 20:59:38 +02:00
README.md [BRANDING] add Forgejo logo 2023-10-09 20:51:47 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-10-09 19:11:01 +02: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 2023-10-09 19:11:02 +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.

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.