Beyond coding. We forge. (Code of Conduct: https://codeberg.org/forgejo/code-of-conduct)
Go to file
Gusted 577aec56fe
[BRANDING] security.txt
- The [security.txt](https://securitytxt.org/) is a standardized file to
help with reporting security vulnerabilities, by having the most essential
information served at `.well-known/security.txt`.
- Brand this file to point to the Forgejo security team.
- Resolves https://codeberg.org/forgejo/forgejo/issues/1192

(cherry picked from commit 7ca1d0ec87)
(cherry picked from commit ba974b0161)
(cherry picked from commit 966fbcdcfd)
(cherry picked from commit 8b9efebc6e)
(cherry picked from commit 91b1c84c18)
(cherry picked from commit 30ade1ea0b)
(cherry picked from commit 15ec35014e)
(cherry picked from commit a5e8bb4a93)
(cherry picked from commit 273b03888f)
(cherry picked from commit 69b6b53fe5)
(cherry picked from commit e22a512fde)
(cherry picked from commit 958b3e4877)
(cherry picked from commit d1ad5daa51)
(cherry picked from commit a4868c4d79)
(cherry picked from commit ce4692d352)
(cherry picked from commit 7cb94c23fd)
(cherry picked from commit 05fa514e14)
(cherry picked from commit be70e50114)
(cherry picked from commit 576997ac9a)
(cherry picked from commit 5ca0898717)
(cherry picked from commit 69db3def99)
2024-01-08 15:54:09 +01:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [CI] push forgejo branches to the specified destination 2024-01-08 13:37:01 +01:00
.gitea [WORKFLOW] yaml issue templates 2024-01-08 14:01:18 +01:00
assets [BRANDING] add Forgejo logo 2024-01-08 14:48:59 +01:00
build Use Set[Type] instead of map[Type]bool/struct{}. (#26804) 2023-08-30 06:55:25 +00:00
cmd [BRANDING] Rebrand dump log 2024-01-08 15:53:09 +01:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2024-01-08 15:54:08 +01:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2024-01-08 15:52:08 +01:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2024-01-08 15:53:09 +01:00
docs Improve frontend guideline (#28711) 2024-01-07 01:14:10 +08:00
models [BRANDING] Use forgejo binary name 2024-01-08 15:54:08 +01:00
modules [BRANDING] parse FORGEJO__* in the container environment 2024-01-08 15:54:08 +01:00
options [BRANDING] Replace links to GitHub with Codeberg guides about adding SSH/GPG keys 2024-01-08 15:54:09 +01:00
public [BRANDING] security.txt 2024-01-08 15:54:09 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2024-01-08 14:01:17 +01:00
routers [BRANDING] Use forgejo binary name 2024-01-08 15:54:08 +01:00
services [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2024-01-08 15:53:09 +01:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [BRANDING] Replace links to GitHub with Codeberg guides about adding SSH/GPG keys 2024-01-08 15:54:09 +01:00
tests [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2024-01-08 15:53:09 +01:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes 2024-01-08 15:52:58 +01:00
.air.toml Reduce verbosity of dev commands (#24917) 2023-05-24 20:11:04 +00:00
.changelog.yml Adapt .changelog.yml to new labeling system (#27701) 2023-10-20 00:22:00 +02:00
.deadcode-out [DEADCODE] update deadcode-out 2024-01-08 14:02:21 +01:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
.gitattributes [META] Use correct language for .tmpl 2024-01-08 14:01:18 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2024-01-08 14:01:19 +01:00
.gitpod.yml Add Github related extensions in devcontainer (#25800) 2023-07-14 15:58:02 +08:00
.golangci.yml Remove go versions from .golangci.yml (#27953) 2023-11-07 22:03:27 +01:00
.ignore Add /public/assets to .ignore (#26232) 2023-07-30 12:34:20 +02:00
.markdownlint.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00: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 (#28537) 2023-12-30 05:29:03 +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 User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
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-01-08 14:01:18 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2024-01-08 14:01:17 +01:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] Forgejo Actions based release process 2024-01-08 13:37:01 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2024-01-08 13:37:01 +01:00
go.mod Upgrade xorm to new version which supported update join for all supported databases (#28590) 2023-12-31 05:00:35 +00:00
go.sum Upgrade xorm to new version which supported update join for all supported databases (#28590) 2023-12-31 05:00:35 +00:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2024-01-08 14:01:17 +01:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2024-01-08 15:53:09 +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-01-08 15:54:08 +01:00
package-lock.json Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
package.json Update JS dependencies (#28537) 2023-12-30 05:29:03 +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 (#28120) 2023-11-20 01:02:57 +01: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. 2024-01-08 15:53:09 +01:00
README.md [BRANDING] add Forgejo logo 2024-01-08 14:48:59 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2024-01-08 14:01:17 +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-01-08 14:01:17 +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.